Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 18 Oct 2013 16:40:45 +0000 (UTC)
From: "Brandon Williams (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12674536.1382107611075.88018.1382114445573@arcas>
In-Reply-To: <JIRA.12674536.1382107611075@arcas>
References: <JIRA.12674536.1382107611075@arcas>
Subject: [jira] [Updated] (CASSANDRA-6217) replace doesn't clean up
 system.peers if you have a new IP
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Brandon Williams updated CASSANDRA-6217:
----------------------------------------

    Fix Version/s:     (was: 1.2.11)
                   1.2.12

> 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.12, 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)