Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <15052143.108591288218501507.JavaMail.jira@thor>
Date: Wed, 27 Oct 2010 18:28:21 -0400 (EDT)
From: "Matthew F. Dennis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Created: (CASSANDRA-1670) cannot decom a node then bring it
 back to the cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
    Affects Versions: 0.7 beta 2
         Environment: RAX
            Reporter: Matthew F. Dennis


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.