[CASSANDRA-15854] Truncation should fail any ongoing repairs

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta3, 4.0
• Component/s: Consistency/Repair
• Bug Category: Correctness - Transient Incorrect Response
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: Code Inspection
• Platform: All
• Since Version: 4.0-alpha1

Source Control Link

https://github.com/apache/cassandra/commit/d4eba9faa1b57fed205813a639fe53bbbdc06ef1

Test and Documentation Plan

new jvm dtest, cci runs

• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

Caleb Rackliffe, David Capwell

• Created: 04/Jun/20 08:55
• Updated: 03/Jan/21 17:03
• Resolved: 25/Sep/20 07:13

Description

Truncation may race with ongoing repairs, making it possible to clear data on one node but then stream data its truncation would have deleted from another node. We should abort any ongoing preview repairs if we get a truncation request.

Issue Links

• is blocked by: CASSANDRA-15851 Add bytebuddy support for in-jvm dtests