You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2011/02/21 20:27:39 UTC

[jira] Updated: (CASSANDRA-1900) Make removetoken force always work

     [ https://issues.apache.org/jira/browse/CASSANDRA-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-1900:
--------------------------------------

    Remaining Estimate: 6h
     Original Estimate: 6h

> Make removetoken force always work
> ----------------------------------
>
>                 Key: CASSANDRA-1900
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1900
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 0.7.0 rc 2, 0.7.0 rc 3
>            Reporter: Nick Bailey
>            Assignee: Brandon Williams
>             Fix For: 0.7.1
>
>         Attachments: 1900-v2.txt, 1900-v3.txt, 1900-v4.txt, 1900.txt
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> The 'removetoken force' command was intended for forcing a removal to complete when the removal stalls for some reason. The most likely reason being a streaming failure causing the node to wait forever for streams to complete.
> The command should be updated so that it can force a removal in any case. For example a node that was decommissioned but killed before a LEFT status was broadcasted. This leaves the node in a permanent 'leaving' state.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira