[
https://issues.apache.org/jira/browse/CASSANDRA-4512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435958#comment-13435958
]
Manoj Kanta Mainali commented on CASSANDRA-4512:
------------------------------------------------
Do you have any concrete steps on how to reproduce this and what is the error
message you get? Did you check the server logs?
I tried truncating after create two instances, killing one of it and removing
its token using the nodetool, but cli didn't report any error and truncation
was successful.
The only reason truncate will throw nodes as UNREACHABLE is if the endpoint
still exists in the down nodes (unreachable) set. If your remove token was
successful and didn't throw any error, the endpoint would be removed from the
unreachable nodes set.
> Nodes removed with removetoken stay around preventing truncation
> ----------------------------------------------------------------
>
> Key: CASSANDRA-4512
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4512
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.0.10
> Environment: Ubuntu, EC2
> Reporter: Taras Ovsyankin
> Priority: Minor
>
> Removed multiple nodes from the cluster in order to scale down (killed VMs
> then ran removetoken for every dead node). Nodetool ring looks happy, but
> cassandra-cli reports removed nodes as UNREACHABLE and truncation doesn't
> work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
