Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <DA6AD352B2C6DC4EAB14CD8FAFB2686417A28748@MMT-SRV-XDB2.mmt.com>
References: <4F98F25C.4060200@syncopated.net>
	<DA6AD352B2C6DC4EAB14CD8FAFB2686417A27092@MMT-SRV-XDB2.mmt.com>
	<DA6AD352B2C6DC4EAB14CD8FAFB2686417A27952@MMT-SRV-XDB2.mmt.com>
	<CACHzRHZkEPCMsNEc0oOSng1KNhxZh_GtEPeGe_Wpvgvtr60XVA@mail.gmail.com>
	<DA6AD352B2C6DC4EAB14CD8FAFB2686417A28748@MMT-SRV-XDB2.mmt.com>
Date: Thu, 26 Apr 2012 22:45:02 -0700
Message-ID: 
 <CACHzRHZK4HrUQeEqUu2G+yvhYizEQAF3pZDw5BZh7vTwdMTvPw@mail.gmail.com>
Subject: Re: Taking a Cluster Wide Snapshot
From: Rob Coli <rcoli@palominodb.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Apr 26, 2012 at 10:38 PM, Shubham Srivastava
<Shubham.Srivastava@makemytrip.com> wrote:
> On another thought I could also try copying the data of my keyspace alone from one node to another node in the new cluster (I have both the old and new clusters having same nodes DC1:6,DC2:6 with same tokens) with the same tokens.
>
> Would there be any risk of the new cluster getting joined to the old cluster probably if the data inside keyspace is aware of the original IP's etc.

As a result of this very concern while @ Digg...

https://issues.apache.org/jira/browse/CASSANDRA-769

tl;dr : as long as your cluster names are unique in your cluster
config (**and you do not copy the System keyspace, letting the new
cluster initialize with the new cluster name**), nodes are at no risk
of joining the wrong cluster.

=Rob

-- 
=Robert Coli
AIM&GTALK - rcoli@palominodb.com
YAHOO - rcoli.palominob
SKYPE - rcoli_palominodb