You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/01/03 19:56:00 UTC
[jira] [Resolved] (CASSANDRA-6547) Patch to bring back
replace_token
[ https://issues.apache.org/jira/browse/CASSANDRA-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-6547.
---------------------------------------
Resolution: Won't Fix
Sorry, I don't think this is worth the complexity to maintain in tree. Consider creating a script around nodetool to look up an address from a token list instead.
> 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
> Attachments: 6547.txt
>
>
> 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)