[jboss-jira] [JBoss JIRA] Commented: (JGRP-1216) S3_PING / FILE_PING: remove failed members

[Bela Ban (JIRA)]

    [ https://jira.jboss.org/browse/JGRP-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12535889#action_12535889 ] 

Bela Ban commented on JGRP-1216:
--------------------------------

- New property 'interval' writes our own data to S3 periodically (if enabled, 0 disables it)
- On a view, we remove all data in the S3 bucket which is not in the view
- If we have a network partition {A,B} and {C,D}, then everybody erases everbody else's data, but the writer task will write everybody's data to S3 again, so a later merge can occur

> S3_PING / FILE_PING: remove failed members
> ------------------------------------------
>
>                 Key: JGRP-1216
>                 URL: https://jira.jboss.org/browse/JGRP-1216
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 2.10
>
>
> 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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira