cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manoj Kanta Mainali (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4512) Nodes removed with removetoken stay around preventing truncation
Date Thu, 16 Aug 2012 13:41:38 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message