On Fri, Feb 14, 2014 at 10:08 AM, Paulo Ricardo Motta Gomes <
paulo.mo...@chaordicsystems.com> wrote:
> But in our case, our cluster was not using VNodes, so this workaround will
> probably not work with VNodes, since you cannot specify the 256 tokens from
> the old node.
>
Sure you can, in a comma delimited list. I plan to write a short blog post
about this, but...
I recommend that anyone using Cassandra, vnodes or not, always explicitly
populate their initial_token line in cassandra.yaml. There are a number of
cases where you will lose if you do not do so, and AFAICT no cases where
you lose by doing so.
If one is using vnodes and wants to do this, the process goes like :
1) set num_tokens to the desired number of vnodes
2) start node/bootstrap
3) use a one liner like jeffj's :
"
nodetool info -T | grep ^Token | awk '{ print $3 }' | tr \\n , | sed -e
's/,$/\n/'
"
to get a comma delimited list of the vnode tokens
4) insert this comma delimited list in initial_token, and comment out
num_tokens (though it is a NOOP)
=Rob
