[
https://issues.jboss.org/browse/JGRP-1956?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1956:
--------------------------------
Can you try with the following attributes enabled: ?
* {{remove_old_coords_on_view_change}}
* {{remove_all_files_on_view_change}}
The reason old members are not immediately removed is that these members could have been
split away, in a network partition, rather than crashed. If we want a merge to succeed in
such a case, it is better to leave information about them in the store.
Note that {{TP.logical_addr_cache_max_size}} and {{TP.logical_addr_cache_expiration}}
govern when stale entries will be removed. By default, you won't have more than 2000
stale elements in the cache.
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)