cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diane Griffith <>
Subject Re: restore a cassandra cluster from snapshot failed
Date Wed, 09 Jul 2014 23:31:33 GMT
Yes the link was to the documentation:

So when you say restore the system column family, do you mean that
keyspace?  Or do you mean the desired target column family.  Via cql, the
target keyspace and column families to be restored are created.

The only files copied over were the sstable files for each applicable
column family.

in cassandra.yaml, the num_tokens parameter is set and set to 256.
initial_token is not set at all and there are no vnode configurations set
either.  The seed list of the cluster is the same as before, everything is
identical as the first time.

Is there a problem that happens if only num_tokens is set?  I did not
remember seeing anything that I needed to set initial_token on clusters in


On Wed, Jul 9, 2014 at 6:54 PM, Robert Coli <> wrote:

> On Wed, Jul 9, 2014 at 3:36 PM, Diane Griffith <>
> wrote:
>> Hope someone can help. We are having issues restoring all nodes of a
>> cassandra 2.0 cluster from a snapshot. I have reviewed the instructions
>> [Restoring from a snapshot][1]
> Was there supposed to be a link here?
> Briefly, did you restore the system column family? Are you using vnodes?
>  Did you set initial_token on the target cluster nodes to be the same as on
> source nodes?
> Use :
> nodetool info -T | grep Token | awk '{print $3}' | paste -s -d,
> To generate a comma delimited list of tokens per node and populate
> initial_token in cassandra.yaml before the first time you start any target
> Cassandra node.
> =Rob

View raw message