Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Sep 2013 13:31:21 +0000 (UTC)
From: "Oleg Anastasyev (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12670272.1380029448256.9197.1380029481293@arcas>
In-Reply-To: <JIRA.12670272.1380029448256@arcas>
References: <JIRA.12670272.1380029448256@arcas>
Subject: [jira] [Created] (CASSANDRA-6086) Node refuses to start with
 exception in ColumnFamilyStore.removeUnfinishedCompactionLeftovers when
 find that some to be removed files are already removed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Oleg Anastasyev created CASSANDRA-6086:
------------------------------------------

             Summary: Node refuses to start with exception in ColumnFamilyStore.removeUnfinishedCompactionLeftovers when find that some to be removed files are already removed
                 Key: CASSANDRA-6086
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6086
             Project: Cassandra
          Issue Type: Bug
            Reporter: Oleg Anastasyev


Node refuses to start with
{code}
Caused by: java.lang.IllegalStateException: Unfinished compactions reference missing sstables. This should never happen since compactions are marked finished before we start removing the old sstables.
      at org.apache.cassandra.db.ColumnFamilyStore.removeUnfinishedCompactionLeftovers(ColumnFamilyStore.java:544)
      at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:262)
{code}

IMO, there is no reason to refuse to start discivering files that must be removed are already removed. It looks like pure bug diagnostic code and mean nothing to operator (nor he can do anything about this).

Replaced throw of excepion with dump of diagnostic warning and continue startup.


--
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: http://www.atlassian.com/software/jira