[
https://issues.apache.org/jira/browse/CASSANDRA-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302871#comment-14302871
]
Erik Forsberg commented on CASSANDRA-6542:
------------------------------------------
I observed this on my 1.2.18 production cluster. 6 out of 56 machines would not
come back with any replication confirmation.
Checking 'nodetool netstats' on the 6 machines, there were no streaming
sessions ongoing. Checking the logs on the 6 machines, they had been streaming
relevant data.
> nodetool removenode hangs
> -------------------------
>
> Key: CASSANDRA-6542
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6542
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Ubuntu 12, 1.2.11 DSE
> Reporter: Eric Lubow
> Assignee: Tyler Hobbs
>
> Running *nodetool removenode $host-id* doesn't actually remove the node from
> the ring. I've let it run anywhere from 5 minutes to 3 days and there are no
> messages in the log about it hanging or failing, the command just sits there
> running. So the regular response has been to run *nodetool removenode
> $host-id*, give it about 10-15 minutes and then run *nodetool removenode
> force*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
