[
https://issues.apache.org/jira/browse/CASSANDRA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118504#comment-13118504
]
Hudson commented on CASSANDRA-3259:
-----------------------------------
Integrated in Cassandra-0.8 #352 (See
[https://builds.apache.org/job/Cassandra-0.8/352/])
Evict gossip state immediately when a token is taken over.
Patch by vijay, reviewed by brandonwilliams for CASSANDRA-3259
brandonwilliams :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1177847
Files :
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/gms/Gossiper.java
*
/cassandra/branches/cassandra-0.8/src/java/org/apache/cassandra/service/StorageService.java
> Replace token leaves the old node state in tact causing problems in cli
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-3259
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3259
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.8.3
> Environment: JVM on CentOS
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 0.8.7, 1.0.0
>
> Attachments: 0001-evict-replaced-node-immediately-v2.patch,
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
