[ https://issues.apache.org/jira/browse/CASSANDRA-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920310#action_12920310
]
Nick Bailey commented on CASSANDRA-1609:
----------------------------------------
So it looks like we don't remove tokens from the system table when we decomission which leads
to the following scenario:
# Node A has token 1
# Node A loadbalance to token 2
# Node A dies
# Node A removed
# Cluster restart
# Node A reappears with token 1 since that was never removed/overwritten in the system table.
At least i think thats how its happening. Not sure about one of our nodes seeing the four
decomissioned tokens and the others not.
> 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: Nick Bailey
> Fix For: 0.7.0
>
>
> 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.
|