cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Carrino (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-6008) Getting 'This should never happen' error at startup due to sstables missing
Date Wed, 11 Sep 2013 21:50:52 GMT
John Carrino created CASSANDRA-6008:

             Summary: Getting 'This should never happen' error at startup due to sstables
                 Key: CASSANDRA-6008
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: John Carrino
             Fix For: 2.0.1

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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message