cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-1216) removetoken drops node from ring before re-replicating its data is finished
Date Tue, 20 Jul 2010 22:38:50 GMT


Nick Bailey updated CASSANDRA-1216:

    Attachment: 0001-Modify-removeToken-command-to-make-it-similar-to-dec.patch

* 0001 - changes to make removeToken behave similarly to decomission
* 0002 - fixes to existing tests since the state for STATE_LEFT changed

I am still working on some good unit tests for these changes but these are the changes so

The new process for removeToken is basically the one outlined above. One change is that instead
of a STATE_REMOVED state it seemed like tokens that are removed should just go into STATE_LEFT
similar to nodes that are decommissioned.

One thing I'm not sure of is the timeout values for waiting for replications to stream and
for waiting for replication notifications. Currently they are just set arbitrarily in that
patch. Need to determine good values for these.

> removetoken drops node from ring before re-replicating its data is finished
> ---------------------------------------------------------------------------
>                 Key: CASSANDRA-1216
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Nick Bailey
>             Fix For: 0.7
>         Attachments: 0001-Modify-removeToken-command-to-make-it-similar-to-dec.patch,
> this means that if something goes wrong during the re-replication (e.g. a source node
is restarted) there is (a) no indication that anything has gone wrong and (b) no way to restart
the process (other than the Big Hammer of running repair)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message