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

["Brandon Williams (Commented) (JIRA)" <ji...@apache.org>]

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

Brandon Williams commented on CASSANDRA-3259:
---------------------------------------------

If this is causing problems in the cli, the cli is doing something wrong, because removeEndpoint already takes it out of the Gossiper's unreachable nodes.  What problem is this solving?

We do need to expire remove this endpoint but I don't think exposing evictFromMembership is the best way.
                
> 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: 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira