DataStax Help Center

Replacement node fails to start with the error "Cannot replace token <number> which does not exist!"


When adding a node into a cluster using the option:


An exception was seen for a non existent token


When following the normal procedure to replace a dead node for example here, the following exception was seen when starting the new node:

ERROR [main] 2015-10-02 13:01:54,230 - Exception encountered during startup
java.lang.UnsupportedOperationException: Cannot replace token -9223372036854775808 which does not exist!
    at org.apache.cassandra.service.StorageService.joinTokenRing( ~[cassandra-all-]
    at org.apache.cassandra.service.StorageService.initServer( ~[cassandra-all-]
    at org.apache.cassandra.service.StorageService.initServer( ~[cassandra-all-]
    at org.apache.cassandra.service.CassandraDaemon.setup( ~[cassandra-all-]
    at com.datastax.bdp.server.DseDaemon.setup( ~[dse.jar:4.7.0]
    at org.apache.cassandra.service.CassandraDaemon.activate( ~[cassandra-all-]
    at com.datastax.bdp.DseModule.main( [dse.jar:4.7.0]
INFO  [Thread-2] 2015-10-02 13:01:54,231 - DSE shutting down...


There is a known issue in Apache Cassandra version 2.1.8 as detailed in the following Cassandra jira: 


The node could be added the following ways:

  • bootstrapping it into the cluster normally (without the -Dcassandra.replace_address option)
  • forced to join the ring by setting auto_bootstrap: false in the cassandra.yaml


Upgrade to DSE4.7.4, 4.8.0 or later which will include Cassandra 2.1.9


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk