[ https://issues.apache.org/jira/browse/CASSANDRA-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695288#comment-17695288 ]
David Capwell commented on CASSANDRA-18292: ------------------------------------------- Was bitten by CASSANDRA-18047 and saw it was caused by us stopping instances without waiting for them to complete... I patched the test as it was a simple fix... > Gossip stateMapOrdering does not have correct ordering when both > EndpointState are in the bootstrapping set > ----------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-18292 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18292 > Project: Cassandra > Issue Type: Bug > Components: Cluster/Gossip > Reporter: David Capwell > Assignee: David Capwell > Priority: Normal > Fix For: 4.x > > > There is a bug when stateMapOrdering sees two or more EndpointState that are > both in the bootstrapping set, this may cause the ordering to change causing > Collections.sort to fail -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org