cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-6217) replace doesn't clean up system.peers if you have a new IP
Date Fri, 18 Oct 2013 15:52:42 GMT

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

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

    Attachment: 6217.txt

Existing nodes will already have the correct peers state due to the token conflict(s) from
the replacer, but the replacer will still have the dead node in its own peers table.  The
simplest thing to do is finish replacing by removing the replace_address from the table, since
either it will be our own (which should not appear there) or it will be the old node.  Trivial
patch to do so.

> 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
>         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)

Mime
View raw message