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

[Bela Ban (JIRA)]

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

Bela Ban commented on JGRP-1956:
--------------------------------

By default, neither attribute is enabled. Especially {{remove_all_files_on_view_change}} causes more network traffic. I suggest enable {{remove_old_coords_on_view_change}} only for now, as this handles members getting killed with kill -9, but doesn't cause as much traffic as enabling the other attr.
Re {{info_writer_max_writes_after_view}}: yes, you're right, 1 should be good enough in most cases. 

> 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)