cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Czech <>
Subject Re: unwanted node discovery
Date Sun, 02 Oct 2011 22:22:26 GMT
Another thing Edward if you don't mind, how does cassandra choose a node to
associate with a token if there is more than one node with the same token?
 I know that's definitely not a favorable situation to be in, but I'm
curious how my production ring chose to switch ownership of the tokens.

On Sun, Oct 2, 2011 at 3:14 PM, Edward Capriolo <>wrote:

> On Sun, Oct 2, 2011 at 4:25 PM, Eric Czech <> wrote:
>> We're exploring a data processing procedure where we snapshot our
>> production cluster data and move that data to a new cluster for analysis but
>> I'm having some strange issues where the analysis cluster is still somehow
>> aware of the production cluster (i.e. the production cluster ring is trying
>> to include nodes from the other cluster with the same token).
>> The seed addresses in cassandra.yaml definitely prohibit this type of
>> intersection between the two clusters so I'm guessing that it has something
>> to do with the information in the system sstables.
>> Is there anyway to duplicate raw sstables in an effort to "copy" a cluster
>> such that the copied cluster has a different name?  I know this usually
>> results in a "saved cluster name X != Y" sort of error but it looks like we
>> need to find some sort of way to do this logical separation.
>> Any help would be much appreciated!
>> Thanks.
> Cassandra stores information about the cluster topology in the system
> table. This is stored in the LocationInfo column family. If you set
> AutoBootstrap to false, assign the Initial Token correctly and wipe the
> LocationInfo column family. Cassandra will have no memory of the topology.
> (You can also wipe the entire system keyspace but then you have to reinstall
> the schema)

View raw message