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

Jean-Michael Cyr commented on CASSANDRA-12485:
----------------------------------------------

Let's say I want my nodes to recover automatically on failure, and I don't want 
to have to add a replace_address option in the bootstrap file.

I think we should be able to expect a node to go down and recover by itself, 
whatever the reason. (Node could be a docker container, or be scheduled to run 
automatic update and reboot, or simply crash and be able to recover..)

I have scripted the whole thing, to add replace_address automatically if the IP 
is found in the system.peers table, even running a nodetool repair 
automatically once the node is fully booted.

Is there something else I should be aware of,  that might punch me in the face 
later ? lol ! 

> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to