[ https://issues.apache.org/jira/browse/CASSANDRA-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920426#action_12920426
]
Nick Bailey commented on CASSANDRA-1609:
----------------------------------------
* handleStateLeft wasn't actually removing the endpoint from gossip before. Was that an oversight
or intended?
* you removed a check from handleStateLeft to make sure the token was a member before removing
it. Intentional?
> Cluster restart re-adds removed tokens
> --------------------------------------
>
> Key: CASSANDRA-1609
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1609
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Reporter: Nick Bailey
> Assignee: Jonathan Ellis
> Fix For: 0.7.0
>
> Attachments: 1609.txt
>
>
> After a cluster restart one of our nodes began reporting tokens that had been removed
a good while ago (week or more) in it's nodetool ring output. This probably has something
to do with our change to persist the ring in CASSANDRA-1518 and removetoken changes in CASSANDRA-1216.
The node didn't actually gossip the removed tokens so they showed up in TMD but not gossip.
> Additionally all nodes began reporting a node that had been removed maybe an hour ago.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|