Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 20 May 2011 08:17:47 +0000 (UTC)
From: "Peter Schuller (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <2045581867.29955.1305879467373.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (CASSANDRA-2674) accidental 'recommission' is too
 easy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

accidental 'recommission' is too easy
-------------------------------------

                 Key: CASSANDRA-2674
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2674
             Project: Cassandra
          Issue Type: Bug
            Reporter: Peter Schuller
            Priority: Minor


(tested on 0.7.5, but I have no reason to believe it's specific)

After decommission, simply restarting the node causes it to pop back into the cluster as Up/Normal without ceremony or streaming, violating consistency in the cluster. This was with autobootstrap enabled in the configuration, and I triggered it specifically for the purpose of testing it, but since the intent was to have that always be turned on anyway (as per CASSANDRA-2447) this is a problem given how easy it is for a node to get started again after a long-running 'decommission' is started. (E.g., host reboots, whatever.)


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira