[CASSANDRA-957] convenience workflow for replacing dead node

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Component/s: Legacy/Tools
• Assignee: Vijay
• Reporter: Jonathan Ellis

Authors

Vijay

Reviewers

Nick Bailey

• Created: 05/Apr/10 22:38
• Updated: 16/Apr/19 09:33
• Resolved: 06/Sep/11 01:14

Description

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?

Issue Links

• depends upon: CASSANDRA-2496 Gossip should handle 'dead' states