[
https://issues.apache.org/jira/browse/CASSANDRA-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843619#action_12843619
]
Jonathan Ellis commented on CASSANDRA-872:
------------------------------------------
I think I remember the reasoning here.
If node x dies, we move its data disks to node y, and start it with a different
IP, we want it to be able to rejoin and pick up w/ HH rather than forcing a
decommission + bootstrap (ouch).
And my first reaction was "okay, so don't do that" (keep IP the same if you're
going to do this) but the problem is that on EC2 using EBS for storage is
basically the only option and you have no control over IPs, so this will bite
you every time if you are changing instance sizes, and IIRC even if your VM's
host restarts.
Someone who actually uses EC2 should correct me if I'm wrong here. :)
> Nodes should fail to join the ring with duped tokens
> ----------------------------------------------------
>
> Key: CASSANDRA-872
> URL: https://issues.apache.org/jira/browse/CASSANDRA-872
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Stu Hood
> Fix For: 0.6, 0.7
>
>
> Currently, multiple nodes can join the ring with the same token (particularly
> when people copy the data directory between machines). The symptom is that
> the new endpoint joins the ring successfully, but both nodes can only see
> themselves in the ring (according to nodetool).
> Instead of this behaviour, we would want gossip to die rather than joining
> with a duped token.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
