[
https://issues.apache.org/jira/browse/CASSANDRA-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788570#comment-13788570
]
Ravi Prasad edited comment on CASSANDRA-5916 at 10/7/13 9:39 PM:
-----------------------------------------------------------------
bq. 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.
my understanding is, due to the generation change of the replacing node,
gossiper.handleMajorStateChange marks the node as dead, as hibernate is one of
the DEAD_STATES. So, the other nodes marks the replacing node as dead before
the token bootstrap starts, hence should be storing hints to the replacing node
from that point. Am i reading it wrong?
was (Author: ravilr):
>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.
my understanding is due to the generation change of the replacing node,
gossiper.handleMajorStateChange marks the node as dead, as hibernate is one of
the DEAD_STATES. So, the other nodes marks the replacing node as dead before
the token bootstrap starts, hence should be storing hints to the replacing node
from that point.
> 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)
