[CASSANDRA-14823] Legacy sstables with range tombstones spanning multiple index blocks create invalid bound sequences on 3.0+

• Type: Bug
• Status: Resolved
• Priority: Urgent
• Resolution: Fixed
• Fix Version/s: 3.0.18, 3.11.4
• Component/s: Local/SSTable
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Critical
• Complexity: Challenging
• Discovered By: Fuzz Test
• Since Version: 3.0.0
• Assignee: Blake Eggleston
• Reporter: Blake Eggleston

Authors

Blake Eggleston

Reviewers

Aleksey Yeschenko, Sam Tunnicliffe

• Created: 12/Oct/18 21:01
• Updated: 02/Aug/19 02:50
• Resolved: 16/Oct/18 19:52

Description

During upgrade from 2.1 to 3.0, reading old sstables in reverse order would generate invalid sequences of range tombstone bounds if their range tombstones spanned multiple column index blocks. The read fails in different ways depending on whether the 2.1 tables were produced by a flush or a compaction.