On Wed, Oct 22, 2014 at 7:58 AM, Li, George <[email protected]>
wrote:
> I assume that you are restoring snapshot data onto a new ring with the
> same topology (i.e. if the old ring has n nodes, your new ring has n nodes
> also). I discussed this a consultant from DataStax, and he told me that I
> need to make sure each new node in the new ring need to have the same token
> list as the corresponding old node in the old ring. For example, if you are
> restoring snapshot from old node 1 onto new node 1, you need to make sure
> new node 1's token list is the same as the token list of the old node 1.
> This can be done by the following main steps:
> 1. Run 'nodetool ring' on the old ring to find token list for each old
> node.
> 2. Stop Cassandra in each new node.
> 3. Modify new ring node 1's yaml file so 'initial_token' is the same as
> the token list of old node 1. Also, set auto_bootstrap to false.
>
>
For vnodes, you can use this handy one-liner to get a comma-delimited list
of tokens for the current node :
nodetool info -T | grep ^Token | awk '{ print $3 }' | tr \\n , | sed -e
's/,$/\n/'
=Rob
http://twitter.com/rcolidba
