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

Tyler Hobbs commented on CASSANDRA-5916:
----------------------------------------

Minor nitpick: you're missing a space before "because" in:
{noformat}
throw new RuntimeException("Cannot replace_address " + 
DatabaseDescriptor.getReplaceAddress() + "because it doesn't exist in gossip");
{noformat}

Other than that, +1

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

Reply via email to