[
https://issues.apache.org/jira/browse/CASSANDRA-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14630614#comment-14630614
]
Stefania commented on CASSANDRA-9765:
-------------------------------------
Cassci has been running here:
http://cassci.datastax.com/job/stef1927-9765-2.0-testall/lastSuccessfulBuild/
http://cassci.datastax.com/job/stef1927-9765-2.0-dtest/lastSuccessfulBuild/
In build #3 there were 3 failed dtests but they failed on the unpatched branch
too (build #92 and #93):
http://cassci.datastax.com/job/cassandra-2.0_dtest/lastCompletedBuild/testReport/
I just merged the dtest pull request and started a new build, #4. Let's see if
we also get the new dtests running on CASSI - if not they did pass on my box.
The 4 new tests live in consistency_test.py, TestConsistency.
> 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)
