[CASSANDRA-6008] Getting 'This should never happen' error at startup due to sstables missing

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Severity: Normal
• Assignee: Tom Hobbs
• Reporter: John Carrino

Authors

Tom Hobbs

Reviewers

Jonathan Ellis

• Created: 11/Sep/13 21:50
• Updated: 16/Apr/19 09:32
• Resolved: 17/Dec/13 18:03

Description

Exception encountered during startup: "Unfinished compactions reference missing sstables. This should never happen since compactions are marked finished before we start removing the old sstables"

This happens when sstables that have been compacted away are removed, but they still have entries in the system.compactions_in_progress table.

Normally this should not happen because the entries in system.compactions_in_progress are deleted before the old sstables are deleted.

However at startup recovery time, old sstables are deleted (NOT BEFORE they are removed from the compactions_in_progress table) and then after that is done it does a truncate using SystemKeyspace.discardCompactionsInProgress

We ran into a case where the disk filled up and the node died and was bounced and then failed to truncate this table on startup, and then got stuck hitting this exception in ColumnFamilyStore.removeUnfinishedCompactionLeftovers.

Maybe on startup we can delete from this table incrementally as we clean stuff up in the same way that compactions delete from this table before they delete old sstables.

Issue Links

• relates to: CASSANDRA-6086 Node refuses to start with exception in ColumnFamilyStore.removeUnfinishedCompactionLeftovers when find that some to be removed files are already removed