cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-872) Nodes should fail to join the ring with duped tokens
Date Wed, 10 Mar 2010 16:39:27 GMT


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

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message