[CASSANDRA-15945] Verify expected SSTable components are present at startup

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 4.0-beta2, 4.0
• Component/s: Local/SSTable
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Low
• Complexity: Normal
• Discovered By: Adhoc Test
• Platform: All
• Since Version: 2.0.0

Source Control Link

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

Test and Documentation Plan

ci

• Assignee: Yifan Cai Assign to me
• Reporter: Yifan Cai

Authors

Yifan Cai

Reviewers

Brandon Williams, David Capwell

• Created: 14/Jul/20 17:36
• Updated: 03/Jan/21 17:03
• Resolved: 20/Jul/20 19:31

Description

When Cassandra batch opens all sstables at startup, it should check that all components listed in the TOC.txt are available. Compression is optional, so there may not be a Compression.db component for all sstables, but if there should be and it's missing we continue to load the sstable. The sstable is unreadable without the compression metadata though, but we won't know this until it's touched by a query or compaction.

To reliably use TOC.txt for verification, it needs CASSANDRA-10709

Issue Links

• is related to: CASSANDRA-15537 4.0 quality testing: Local Read/Write Path: Upgrade and Diff Test