[CASSANDRA-13620] Don't skip corrupt sstables on startup

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.15, 3.11.1, 4.0-alpha1, 4.0
• Component/s: Local/SSTable
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Normal
• Assignee: Marcus Eriksson
• Reporter: Marcus Eriksson

Authors

Marcus Eriksson

Reviewers

Ariel Weisberg

• Created: 19/Jun/17 12:02
• Updated: 15/May/20 08:02
• Resolved: 28/Aug/17 13:43

Description

If we get an IOException when opening an sstable on startup, we just skip it and continue starting

we should use the DiskFailurePolicy and never explicitly catch an IOException here

Issue Links

• duplicates: CASSANDRA-7377 Should be an option to fail startup if corrupt SSTable found