cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1900) Make removetoken force always work
Date Tue, 25 Jan 2011 02:35:44 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986192#action_12986192
] 

Jonathan Ellis commented on CASSANDRA-1900:
-------------------------------------------

can we initialize replicatingNodes to an empty list/set so we don't risk NPEs instead?

> 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.txt
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message