[CASSANDRA-19262] Handle MIN_TOKEN placement correctly

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.1
• Component/s: Consistency/Bootstrap and Decommission
• Bug Category: Correctness - Consistency
• Severity: Critical
• Complexity: Challenging
• Discovered By: Fuzz Test
• Platform: All
• Since Version: 5.1

Source Control Link

https://github.com/apache/cassandra/commit/1cb6d3568b0ab9c7ea5a90b56e680d5b79c1d216

Test and Documentation Plan

Includes new MIN_TOKEN stress test

• Assignee: Alex Petrov
• Reporter: Alex Petrov

Authors

Alex Petrov

Reviewers

Alex Petrov, Sam Tunnicliffe

• Created: 11/Jan/24 09:04
• Updated: 29/Jan/24 15:02
• Resolved: 29/Jan/24 15:02

Description

During concurrent range movements, it is possible to end up in a situation when from the perspective of the node that owns the MIN token, there are two independent ranges (MIN, A] and (Z, MIN]. And from the perspective of the joining node, it does not know that these are two separate ranges, and thinks they are just one wraparound range, so it tries to just add some placements there.

Issue Links

• links to: Trunk PR