On Wed, May 27, 2015 at 5:48 AM, Thomas Whiteway <
thomas.white...@metaswitch.com> wrote:
> I’ve been investigating using replace_address to replace a node that
> hasn’t left the cluster cleanly and after upgrading from 2.1.0 to 2.1.4 it
> seems that adding a new node will automatically replace an existing node
> with the same IP address even if replace_address isn’t used. Does anyone
> know whether this is an expected change (as far as I can tell it doesn’t
> seem to be)?
>
This is a longstanding known issue ("Cassandra has had this behavior since
the inception of decom"), with a fix recently (May 19, 2015) merged to
trunk.
https://issues.apache.org/jira/browse/CASSANDRA-8801
The basic problem is that the node does not forget its own cluster
membership information, and so joins the cluster using its stored tokens.
In my opinion, "decommission" should wipe all stored node state, but 8801
creates a workaround that addresses this, the worst case.
=Rob
