[CASSANDRA-808] Need a way to skip corrupted data in SSTables

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Won't Fix
• Assignee: Unassigned
• Reporter: Stu Hood
• Created: 18/Feb/10 21:45
• Updated: 16/Apr/19 09:33
• Resolved: 12/Apr/11 17:58

Description

The new SSTable format will allow for checksumming of the data file, but as it stands, we don't have a better way to handle the situation than throwing an Exception indicating that the data is unreadable.

We might want to add an option (triggerable via a command line flag?) to Cassandra that will allow for skipping of corrupted keys/blocks in SSTables, to pretend they don't exist rather than throwing the Exception.

An administrator could temporarily enable the option and trigger a compaction to perform a local repair of data, or they could leave it enabled constantly for hands-off recovery.

Issue Links

• depends upon: CASSANDRA-674 New SSTable Format