You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2013/10/18 18:14:42 UTC

[jira] [Resolved] (CASSANDRA-6217) replace doesn't clean up system.peers if you have a new IP

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

Brandon Williams resolved CASSANDRA-6217.
-----------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.2
                   1.2.11
         Reviewer: Jeremiah Jordan  (was: Tyler Hobbs)

Committed.

> replace doesn't clean up system.peers if you have a new IP
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-6217
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6217
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeremiah Jordan
>            Assignee: Brandon Williams
>             Fix For: 1.2.11, 2.0.2
>
>         Attachments: 6217.txt
>
>
> When you use replace_token (or replace_node or replace_address) if the new node has a different IP, the old node will still be in system.peers



--
This message was sent by Atlassian JIRA
(v6.1#6144)