Thanks, Aaron and Tim


Yes. I am trying to decommision a seed node. Looks like the only way to prevent a seed node automatically join the previous cluster on backup is to change its cluster_name


Zaili Xu


From: aaron morton []
Sent: Monday, October 01, 2012 5:34 PM
Subject: Re: Remove node from cluster and have it run as a single node cluster by itself


The other nodes may be trying to connect to it - it may be listed as a
seed node on the other machines?

The other nodes will be looking for it. 


Change the Cluster Name in the yaml file. 





Aaron Morton

Freelance Developer



On 30/09/2012, at 12:04 AM, Tim Wintle <> wrote:

On Fri, 2012-09-28 at 18:53 +0000, Xu, Zaili wrote:


I have an existing Cassandra Cluster. I removed a node from the cluster. Then I decommissioned the removed node, stopped it,  updated its config so that it only has itself as the seed and in the file, even deleted the data, commitlog, and saved_caches. But as soon as I start it backup it is able to join back to the cluster.  How does this node know the information of the existing cluster and was able to join it ?

The other nodes may be trying to connect to it - it may be listed as a
seed node on the other machines?



IMPORTANT: Any information contained in this communication is intended for the use of the named individual or entity. All information contained in this communication is not intended or construed as an offer, solicitation, or a recommendation to purchase any security. Advice, suggestions or views presented in this communication are not necessarily those of Pershing LLC nor do they warrant a complete or accurate statement.

If you are not an intended party to this communication, please notify the sender and delete/destroy any and all copies of this communication. Unintended recipients shall not review, reproduce, disseminate nor disclose any information contained in this communication. Pershing LLC reserves the right to monitor and retain all incoming and outgoing communications as permitted by applicable law.

Email communications may contain viruses or other defects. Pershing LLC does not accept liability nor does it warrant that email communications are virus or defect free.