You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/10/28 19:08:38 UTC

[jira] [Commented] (CASSANDRA-6257) Safety check on node joining cluster (based on last seen vs GC grace period) to avoid zombie data

    [ https://issues.apache.org/jira/browse/CASSANDRA-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807029#comment-13807029 ] 

Brandon Williams commented on CASSANDRA-6257:
---------------------------------------------

Not a bad idea in theory, and with CASSANDRA-5916 done, this shouldn't be too hard.  We already shadow gossip to prevent bootstrapping when the state exists, so we could extends this to always shadow gossip, then compare the heartbeat to the current time.

> Safety check on node joining cluster (based on last seen vs GC grace period) to avoid zombie data
> -------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6257
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6257
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Johnny Miller
>            Priority: Minor
>
> When a node is rejoining a cluster, it would be nice to have some form of safety check that the cluster recognises the last time the node was part of the cluster is greater that the GC grace period and therefore should not be able to rejoin the cluster unless the administrator specifically requests it.
> The goal of this is to help avoid the potential issues with deleted data coming back from the rejoining nodes dataset.



--
This message was sent by Atlassian JIRA
(v6.1#6144)