[jira] [Updated] (CASSANDRA-18292) Gossip stateMapOrdering does not have correct ordering when both EndpointState are in the bootstrapping set

["David Capwell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-18292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Capwell updated CASSANDRA-18292:
--------------------------------------
     Bug Category: Parent values: Correctness(12982)Level 1 values: Unrecoverable Corruption / Loss(13161)
       Complexity: Low Hanging Fruit
    Discovered By: Shadow Traffic
    Fix Version/s: 4.x
         Severity: Critical
         Assignee: David Capwell
           Status: Open  (was: Triage Needed)

made 4.x with critical as I think that means 4.2...

> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org