You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Yuji Ito (JIRA)" <ji...@apache.org> on 2016/11/25 01:28:58 UTC

[jira] [Created] (CASSANDRA-12955) failure node rejoin

Yuji Ito created CASSANDRA-12955:
------------------------------------

             Summary: failure node rejoin
                 Key: CASSANDRA-12955
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12955
             Project: Cassandra
          Issue Type: Bug
          Components: Streaming and Messaging
         Environment: Cassandra 2.2.8
Amazon Linux AMI 2016.03
            Reporter: Yuji Ito
            Priority: Minor


A failure node can rejoin a cluster after killing all nodes and restarting a seed node.

Failure node is a node whose Cassandra data (/var/lib/cassandra) is removed.
The failure node is refused to rejoin the cluster without killing & restarting other nodes because its address already exists.
However, it is possible to rejoin the cluster after killing all nodes and restarting seed nodes.

*cluster*:
* C* 2.2.8
* a cluster has node1, 2, 3
* node1 is a seed
* replication_factor: 3

*how to*:
# stop C* process and delete all data in /var/lib/cassandra on node2 ($sudo rm -rf /var/lib/cassandra/*)
# stop C* process on node1 and node3
# restart C* on node1
# restart C* on node2

Node 2 (failure node) can rejoin the cluster at 4):
{noformat}
$ nodetool status
Datacenter: datacenter1 =======================
Status=Up/Down |/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID Rack
DN [node3 IP] ? 256 100.0% 325553c6-3e05-41f6-a1f7-47436743816f rack1
UN [node2 IP] 7.76 MB 256 100.0% 05bdb1d4-c39b-48f1-8248-911d61935925 rack1
UN [node1 IP] 416.13 MB 256 100.0% a8ec0a31-cb92-44b0-b156-5bcd4f6f2c7b rack1
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)