[
https://issues.apache.org/jira/browse/CASSANDRA-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926469#action_12926469
]
Mike Bulman commented on CASSANDRA-1670:
----------------------------------------
Because move is decommission+bootstrap, the same behavior occurs when moving
node1 as well.
> cannot decom a node then bring it back to the cluster
> -----------------------------------------------------
>
> Key: CASSANDRA-1670
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1670
> Project: Cassandra
> Issue Type: Bug
> Environment: RAX
> Reporter: Matthew F. Dennis
> Priority: Minor
> Fix For: 0.7.1
>
>
> two node cluster (node0, node1). node0 is listed as the only seed on both
> nodes. Listen addresses explicitly set to an IP on both nodes. No initial
> token, no autobootstrap (but see below). Bring up the ring. Everything is
> fine on both nodes.
> decom node1. verify decom completed correctly by reading the logs on both
> nodes. rm all data/logs on node1. bring node1 up again.
> One of two things happen:
> * node0 thinks it is in a ring by itself, node1 thinks both nodes are in the
> ring.
> * both node0 and node1 think they are in rings by themselves
> If you restart node0 after decom, it appears to work normally.
> Similar issues seem to present if you kill node1 (either when
> autobootstrapping before it completes or after it is in the ring) and
> removetoken.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
