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

[Karsten Ohme (JIRA)]

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

Karsten Ohme commented on JGRP-1956:
------------------------------------

Is it possible to define some sensible defaults for handling zombies, e.g. enabling remove_old_coords_on_view_change and remove_all_files_on_view_change? Otherwise a cron job has to be added to clean up stale files from time to time when server instances are crashing?
The default value for `info_writer_max_writes_after_view` is 2. Why is 1 not enough? Does it not try it until it succeeds?

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