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-5916) gossip and tokenMetadata get hostId out of sync on failed replace_node with the same IP address
Date Thu, 17 Oct 2013 21:14:42 GMT

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

Brandon Williams updated CASSANDRA-5916:
----------------------------------------

    Attachment: 5916-v4.txt

v4 fixes the NP3 and throws when autobootstrap is disabled.  The second issue wasn't because
of the replace_address, but because of checks in sendGossip.  v4 just manually sends the message
to all seeds.  Depending on how many seeds you had, that may also fix the last issue (if the
node being replaced is the only seed, obviously that can't work.)

> gossip and tokenMetadata get hostId out of sync on failed replace_node with the same
IP address
> -----------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5916
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5916
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.2.12
>
>         Attachments: 5916.txt, 5916-v2.txt, 5916-v3.txt, 5916-v4.txt
>
>
> If you try to replace_node an existing, live hostId, it will error out.  However if you're
using an existing IP to do this (as in, you chose the wrong uuid to replace on accident) then
the newly generated hostId wipes out the old one in TMD, and when you do try to replace it
replace_node will complain it does not exist.  Examination of gossipinfo still shows the old
hostId, however now you can't replace it either.



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

Mime
View raw message