cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3259) Replace token leaves the old node state in tact causing problems in cli
Date Fri, 30 Sep 2011 19:41:45 GMT


Vijay commented on CASSANDRA-3259:

The problem is that, when we do the replace token we dont change the status of the old node
(to removed ip or something)... hence the Node will get the State back as it is still gossiping
about the replaced node. Even if removeToken() the states are not removed and hence if someone
is talking about this node after (Async evict by doStatus()) this node will be added back....
hence the node will never go out of the Application State. This patch will instead will evict
immediately when it sees a irrelevant host. This is simpler solution than adding another status
like "remove ip". This works as expected in my tests.
> Replace token leaves the old node state in tact causing problems in cli
> -----------------------------------------------------------------------
>                 Key: CASSANDRA-3259
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: JVM on CentOS
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.0.0
>         Attachments: 0001-evict-replaced-node-immediately.patch
> in the replace token patch we dont evict the node from the Gossip which will leave the
node lingering around and causes issues in cli (UNReachable nodes)
> As a part of the replace token if the token is replaced with another token we should
remove the old nodes Gossip states.

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