[
https://issues.apache.org/jira/browse/CASSANDRA-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923999#action_12923999
]
Nick Bailey commented on CASSANDRA-1650:
----------------------------------------
So removetoken blocks for all new replicas to confirm they have the data for
the node being removed. You can actually run "removetoken status" to see which
nodes are being waited on. Since a dropped confirm message or stream request
could cause it to block forever you can run "removetoken force" to finish a
removal already in progress.
There could be a bug here as well or possibly a dropped message?
There should probably be new documentation about this in the wiki.
> removetoken is broken
> ---------------------
>
> Key: CASSANDRA-1650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1650
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Brandon Williams
> Fix For: 0.7.0
>
>
> When running removetoken on a dead node, it hangs forever. The debug log
> shows:
> DEBUG 19:45:53,794 Node /10.179.111.137 ranges
> [(115049868157599339472315320703867977321,62676456546693435176060154681903071729]]
> DEBUG 19:45:53,795 Range
> (115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> will be responsibility of cassandra-1/10.179.65.102
> DEBUG 19:45:53,798 Pending ranges:
> cassandra-1/10.179.65.102:(115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> DEBUG 19:45:53,798 Node /10.179.111.137 ranges
> [(115049868157599339472315320703867977321,62676456546693435176060154681903071729]]
> DEBUG 19:45:53,799 Range
> (115049868157599339472315320703867977321,62676456546693435176060154681903071729]
> will be responsibility of cassandra-1/10.179.65.102
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
