cassandra-commits mailing list archives

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


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

View raw message