Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 8 Nov 2013 22:32:17 +0000 (UTC)
From: "J. Ryan Earl (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12668155.1378936216830.44834.1383949937822@arcas>
In-Reply-To: <JIRA.12668155.1378936216830@arcas>
References: <JIRA.12668155.1378936216830@arcas>
Subject: [jira] [Comment Edited] (CASSANDRA-6008) Getting 'This should never
 happen' error at startup due to sstables missing
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

J. Ryan Earl edited comment on CASSANDRA-6008 at 11/8/13 10:30 PM:
-------------------------------------------------------------------

We were able to recover the node by deleting all the data, commit, and saved_cache directories on the affected node and letting it rebuild.


was (Author: jre):
We were able to recover the node by deleting all the data and commit directories on the affected node and letting it rebuild.

> 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)