[
https://issues.jboss.org/browse/JGRP-1956?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1956:
--------------------------------
No, all files will be removed. The info sender task will cause each coordinator to write
its own information to the store again after a view change, based on
{{info_writer_max_writes_after_view}} and {{info_writer_sleep_time}}. The former attribute
governs the number of times this info is written, with a sleep (the latter attr)
in-between.
S3_PING / FILE_PING: remove failed members
------------------------------------------
Key: JGRP-1956
URL:
https://issues.jboss.org/browse/JGRP-1956
Project: JGroups
Issue Type: Bug
Affects Versions: 3.6.4
Reporter: Karsten Ohme
Assignee: Bela Ban
Fix For: 3.6.5
When we terminate a member (EC2's "terminate" function) or kill -9 it, then
the file (or bucket data in S3) won't get removed. This leads to stale data. On EC2, I
expect that virtualized instances are often simply terminated, so this problem is
compounded there.
SOLUTION:
- Periodically write own data to the file system (FILE_PING) or S3 (S3_PING)
- On a view change: remove all data that's not in the current view
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)