cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Bailey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-1609) Cluster restart re-adds removed tokens
Date Tue, 12 Oct 2010 17:25:32 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920264#action_12920264
] 

Nick Bailey commented on CASSANDRA-1609:
----------------------------------------

So the first 4 tokens were removed using decomission and the last one using removetoken. It
doesn't look like either of those processes remove nodes from the saved state. The nodes then
show up in nodetool ring but not gossip since they don't actually have an application state
to begin with.

> 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.


Mime
View raw message