[CASSANDRA-7939] checkForEndpointCollision should ignore joining nodes

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.0.11, 2.1.1
• Severity: Low
• Assignee: Brandon Williams
• Reporter: Brandon Williams

Authors

Brandon Williams

Reviewers

T Jake Luciani

• Created: 16/Sep/14 00:09
• Updated: 16/Apr/19 09:31
• Resolved: 29/Sep/14 14:53

Description

If you fail a bootstrap, then immediately retry it, cFEC erroneously tells you to replace it:

ERROR 00:04:50 Exception encountered during startup
java.lang.RuntimeException: A node with address bw-3/10.208.8.63 already exists, cancelling join. Use cassandra.replace_address if you want to replace this node.
    at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:453) ~[main/:na]
    at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:666) ~[main/:na]
    at org.apache.cassandra.service.StorageService.initServer(StorageService.java:614) ~[main/:na]
    at org.apache.cassandra.service.StorageService.initServer(StorageService.java:507) ~[main/:na]
    at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:338) [main/:na]
    at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:457) [main/:na]
    at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:546) [main/:na]

Issue Links

• breaks: CASSANDRA-9765 checkForEndpointCollision fails for legitimate collisions
• relates to: CASSANDRA-7069 Prevent operator mistakes due to simultaneous bootstrap