Hi Rob, If you are replacing an address, you need to use the identical > initial_token to the node you are replacing, not the token -1.
Thanks, I hope that does the trick. Btw.. was my idea of how to get at the initial token of the missing/dead node correct? .i.e. nodetool ring | grep 10.10.1.98 | head -1 I want to be sure I'm using the right token. Thanks Tim On Tue, Jun 3, 2014 at 1:45 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Jun 3, 2014 at 8:41 AM, Curious Patient <mongoma...@gmail.com> > wrote: > >> I then started following this documentation on how to replace the node: >> [ >> http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_replace_node_t.html?scroll=task_ds_aks_15q_gk][1 >> ] >> > ... > >> And set the initial token of the new install as the token -1 of the node >> I'm trying to replace in cssandra.yaml: >> ... >> [root@web2:/etc/alternatives/cassandrahome] #./bin/cassandra -f >> -Dcassandra.replace_address=10.10.1.98 >> ... >> The documentation I link to above says to use the replace_address >> directive on the command line rather than cassandra-env.sh if you have a >> tarball install (which we do) as opposed to a package install. >> > > If you are replacing an address, you need to use the identical > initial_token to the node you are replacing, not the token -1. > > =Rob >
