[
https://issues.apache.org/jira/browse/CASSANDRA-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788523#comment-13788523
]
Brandon Williams commented on CASSANDRA-5916:
---------------------------------------------
First, thanks for testing, [~ravilr]!
bq. does it make sense to allow the operator to specify replace_token with the
token(s) along with the replace_address to recover
That could work, but I find it a bit ugly and confusing, especially since
replace_token alone is supposed to work right now, but does not.
bq. 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.
That is true regardless of shadow mode though, since hibernate is a dead state
and the node doesn't go live to reset the hint timer until the replace has
completed.
> 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)
