[CASSANDRA-16628] Logging bug during the node replacement and token assignment

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.25, 3.11.11, 4.0-rc2
• Component/s: Local/Other
• Bug Category: Correctness
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra/commit/8fd046f2557e4d50e80986b813bc904dce625e6a

Test and Documentation Plan

not needed

• Assignee: Brandon Williams Assign to me
• Reporter: Jai Bheemsen Rao Dhanwada

Authors

Brandon Williams

Reviewers

Brandon Williams

• Created: 23/Apr/21 21:44
• Updated: 23/Apr/21 23:12
• Resolved: 23/Apr/21 23:12

Description

Hello Team,

 

I noticed a minor logging issue when a Cassandra node is trying to boot-up with a new IP address but the existing data directory. The IP address and Token fields are inter-changed.

 

Sample Log: 

WARN [GossipStage:1] 2021-04-23 18:24:06,348 StorageService.java:2425 - Not updating host ID 27031833-5141-46e0-b032-bef67137ae49 for /10.24.3.9 because it's mine
INFO [GossipStage:1] 2021-04-23 18:24:06,349 StorageService.java:2356 - Nodes () and /10.24.3.9 have the same token /10.24.3.10. Ignoring -1124147225848710462
INFO [GossipStage:1] 2021-04-23 18:24:06,350 StorageService.java:2356 - Nodes () and /10.24.3.9 have the same token /10.24.3.10. Ignoring -1239985462983206335

Steps to Reproduce:

Replace a Cassandra node with the a new IP address with the same data directory and the logs should show the messages.

Cassandra Version: 3.11.6

 

Please let me know if you need more details