Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 22 Sep 2016 19:14:21 +0000 (UTC)
From: "Christopher Licata  (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12998072.1471480561000.641503.1474571661493@Atlassian.JIRA>
In-Reply-To: <JIRA.12998072.1471480561000@Atlassian.JIRA>
References: <JIRA.12998072.1471480561000@Atlassian.JIRA> <JIRA.12998072.1471480561668@arcas>
Subject: [jira] [Commented] (CASSANDRA-12485) Always require replace_address
 to replace existing token
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 22 Sep 2016 19:14:23 -0000


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

Christopher Licata  commented on CASSANDRA-12485:
-------------------------------------------------

Hey Paulo, I am going to try to take on this task, but I think I am misunderstanding the scenario in which a node will take over the tokens from another node during replacement.  Could you please explain it a bit more as this will be my first attempt at a contribution to this project?

> Always require replace_address to replace existing token
> --------------------------------------------------------
>
>                 Key: CASSANDRA-12485
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12485
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: Paulo Motta
>            Priority: Minor
>              Labels: lhf
>
> CASSANDRA-10134 prevented replace an existing node unless {{\-Dcassandra.replace_address}} or {{\-Dcassandra.allow_unsafe_replace=true}} is specified.
> We should extend this behavior to tokens, preventing a node from joining the ring if another node with the same token already existing in the ring, unless {{\-Dcassandra.replace_address}} or {{\-Dcassandra.allow_unsafe_replace=true}} is specified in order to avoid catastrophic scenarios.
> One scenario where this can easily happen is if you replace a node with another node with a different IP, and after some time you restart the original node by mistake. The original node will then take over the tokens of the replaced node (since it has a newer gossip generation).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)