cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6008) Getting 'This should never happen' error at startup due to sstables missing
Date Wed, 20 Nov 2013 16:43:39 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827832#comment-13827832
] 

Tyler Hobbs commented on CASSANDRA-6008:
----------------------------------------

I can reproduce this fairly consistently (on trunk, at least) using only {{cassandra-stress}}.
 Just let it run for a few minutes, CTRL-C the cassandra process, then restart it.

> Getting 'This should never happen' error at startup due to sstables missing
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6008
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6008
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: John Carrino
>            Assignee: Yuki Morishita
>             Fix For: 2.0.3
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message