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 Wed, 31 Aug 2011 05:09:15 GMT


Vijay updated CASSANDRA-957:

    Attachment:     (was: 0003-making-bootstrap-sleep-longer.patch)

> convenience workflow for replacing dead node
> --------------------------------------------
>                 Key: CASSANDRA-957
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Core, Tools
>    Affects Versions: 0.8.2
>            Reporter: Jonathan Ellis
>            Assignee: Vijay
>             Fix For: 1.0
>         Attachments: 0001-Support-bringing-back-a-node-to-the-cluster-that-exi.patch,
0001-support-for-replace-token-v3.patch, 0001-support-token-replace-v4.patch, 0001-support-token-replace-v5.patch,
0002-Do-not-include-local-node-when-computing-workMap.patch, 0002-hints-on-token-than-ip-v4.patch,
0002-hints-on-token-than-ip-v5.patch, 0002-upport-for-hints-on-token-v3.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