[CASSANDRA-17676] When a node is bootstrapping it gets the whole gossip state but applies in random order causing some cases where StorageService will fail causing an instance to not show up in TokenMetadata

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.0-alpha1, 5.0
• Component/s: Cluster/Gossip
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Normal
• Complexity: Normal
• Discovered By: Adhoc Test
• Platform: All
• Since Version: 2.0.0

Source Control Link

https://github.com/apache/cassandra/commit/2dcf7d221672ce5ca15dbeb666a8fedb7ec805ff

Test and Documentation Plan

manual testing

• Assignee: David Capwell
• Reporter: David Capwell

Authors

David Capwell

Reviewers

Blake Eggleston

• Created: 31/May/22 23:21
• Updated: 12/Sep/23 13:03
• Resolved: 01/Jun/22 17:51

Description

When gossip state has a causal relationship, the order the state gets applied needs to match this relationship, and when it doesn’t it can cause bootstrap (which apply the whole state in an empty state) to see missing data or instances

Issue Links

• is related to: CASSANDRA-18292 Gossip stateMapOrdering does not have correct ordering when both EndpointState are in the bootstrapping set
• links to: CI: trunk
• links to: PR: trunk