[ https://issues.apache.org/jira/browse/CASSANDRA-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629089#comment-14629089 ]
Stefania commented on CASSANDRA-9765: ------------------------------------- Thanks for the clarifications. I cleaned up {{isSafeForBootstrap}} and implemented the nits in the [latest commit|https://github.com/stef1927/cassandra/commit/ba9a69ea21b6cf2e70408ba62522a4a58b695e3f]. > checkForEndpointCollision fails for legitimate collisions > --------------------------------------------------------- > > Key: CASSANDRA-9765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9765 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: Richard Low > Assignee: Stefania > Fix For: 2.0.17 > > > Since CASSANDRA-7939, checkForEndpointCollision no longer catches a > legitimate collision. Without CASSANDRA-7939, wiping a node and starting it > again fails with 'A node with address %s already exists', but with it the > node happily enters joining state, potentially streaming from the wrong place > and violating consistency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)