[CASSANDRA-8960] Suspect SSTable status is lost when rewriter is aborted

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Duplicate
• Severity: Low
• Assignee: Unassigned Assign to me
• Reporter: Branimir Lambov
• Created: 12/Mar/15 10:23
• Updated: 16/Apr/19 09:31
• Resolved: 02/Jul/15 10:24

Description

This can cause repeated compaction failures and buildup if an SSTable opens correctly but fails during iteration. The exception will trigger a writer.abort() in CompactionTask, which in turn will replace suspect tables with clones obtained through cloneWithNewStart(). The latter does not copy suspect status, hence the node no longer knows that reading from this table has failed.

Issue Links

• duplicates: CASSANDRA-9478 SSTables are not always properly marked suspected