Fabien Rousseau created CASSANDRA-6547:
------------------------------------------

             Summary: Patch to bring back replace_token
                 Key: CASSANDRA-6547
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6547
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Fabien Rousseau


This is a follow-up for CASSANDRA-5916 where option "-Dcassandra.replace_token" 
was deprecated.

The attached patch is a tentative to bring it back, but the token(s) must 
identify only one host and be an exact match (ie : all tokens of the host must 
be specified).

How it works:
 - after the shadow gossip round, it tries to find a host to replace which 
matches exactly the specified tokens.
 - then it set -Dcassandra.replace_address
 - then, process is the same as replacing an host

For us, it is a lot easier to use replace_token than replace_address. (We 
describe a cluster with a number of nodes and a list of tokens, and are in the 
cloud...)






--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to