[jira] [Updated] (CASSANDRA-3259) Replace token leaves the old node state in tact causing problems in cli

["Vijay (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vijay updated CASSANDRA-3259:
-----------------------------

    Attachment: 0002-evict-during-replace-token-for-1.0.patch

Hi Brandon, Really sorry about extra work... i missed one change for 1.0 i was separating these 2 patches and some how i missed it.... 
                
> 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, 0002-evict-during-replace-token-for-1.0.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