cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnny Miller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6257) Safety check on node joining cluster (based on last seen vs GC grace period) to avoid zombie data
Date Mon, 28 Oct 2013 18:08:51 GMT

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

Johnny Miller commented on CASSANDRA-6257:
------------------------------------------

Just to provide some clarification on the scenario behind this.

The recommended action when returning a node to a cluster when it has been out for longer
than the GC grace period is to remove the node, wipe its data and then rejoin. The purpose
of this improvement is to ensure that if this isn't done, we at least warn the admin unless
they explicitly want it.

> 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
>            Assignee: Tyler Hobbs
>            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)

Mime
View raw message