cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-957) convenience workflow for replacing dead node
Date Sun, 10 Jul 2011 00:12:00 GMT


Vijay updated CASSANDRA-957:

    Attachment: 0003-Make-HintedHandoff-More-reliable.patch

Adding support for replacing token.... This also supports replacement with the same IP. Reworked
Hints to be based on Token instead of IP's.... The 3rd part of the patch also makes the hints
be delivered to the host (currently seems like it is not delivered at all... Let me know if
you want to move this to a different ticket).

> convenience workflow for replacing dead node
> --------------------------------------------
>                 Key: CASSANDRA-957
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core, Tools
>            Reporter: Jonathan Ellis
>             Fix For: 1.0
>         Attachments: 0001-Support-Token-Replace.patch, 0001-Support-bringing-back-a-node-to-the-cluster-that-exi.patch,
0002-Do-not-include-local-node-when-computing-workMap.patch, 0002-Rework-Hints-to-be-on-token.patch,
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> 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.
For more information on JIRA, see:


View raw message