cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5916) gossip and tokenMetadata get hostId out of sync on failed replace_node with the same IP address
Date Sun, 29 Sep 2013 22:46:26 GMT

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

Ravi Prasad commented on CASSANDRA-5916:
----------------------------------------

Tested the patch applied against 1.2.10 and it works. Hints replay also works now after replace/bootstrap.
 Regarding the corner case, where replace fails to finish after gossiper started with new
generation, hence knocking out the TOKENS state,  does it make sense to allow the operator
to specify replace_token with the token(s) along with the replace_address to recover from
such scenario. the token list is logged during the first attempt already.
I think remaining in shadow mode may not work optimally well for cases where the node being
replaced was down for more than hint window. So, all the nodes would have stopped hinting,
and after replace, it would require repair to be ran to get the new data fed during the replace.


> 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.11
>
>         Attachments: 5916.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