Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 28 Oct 2013 18:08:41 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12676181.1382983090704.12297.1382983721150@arcas>
In-Reply-To: <JIRA.12676181.1382983090704@arcas>
References: <JIRA.12676181.1382983090704@arcas>
Subject: [jira] [Assigned] (CASSANDRA-6257) Safety check on node joining
 cluster (based on last seen vs GC grace period) to avoid zombie data
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Williams reassigned CASSANDRA-6257:
-------------------------------------------

    Assignee: Tyler Hobbs

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