convenience workflow for replacing dead node
--------------------------------------------
Key: CASSANDRA-957
URL: https://issues.apache.org/jira/browse/CASSANDRA-957
Project: Cassandra
Issue Type: Wish
Components: Core, Tools
Reporter: Jonathan Ellis
Fix For: 0.8
Replacing a dead node with a new one is a common operation, but "nodetool
removetoken" followed by bootstrap is inefficient (re-replicating data first to
the remaining nodes, then to the new one) and manually bootstrapping to a token
"just less than" the old one's, followed by "nodetool removetoken" is slightly
painful and prone to manual errors.
First question: how would you expose this in our tool ecosystem? It needs to
be a startup-time option to the new node, so it can't be nodetool, and messing
with the config xml definitely takes the "convenience" out. A one-off
-DreplaceToken=XXY argument?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
