[CASSANDRA-5916] gossip and tokenMetadata get hostId out of sync on failed replace_node with the same IP address

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.11, 2.0.2
• Severity: Normal
• Since Version: 1.2.0
• Assignee: Brandon Williams
• Reporter: Brandon Williams

Authors

Brandon Williams

Reviewers

Tom Hobbs

• Created: 21/Aug/13 17:12
• Updated: 16/Apr/19 09:32
• Resolved: 18/Oct/13 02:08

Description

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.

Issue Links

• blocks: CASSANDRA-5571 Reject bootstrapping endpoints that are already in the ring with different gossip data