Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 28 Sep 2017 21:13:00 +0000 (UTC)
From: "Blake Eggleston (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13105867.1506633143000.230329.1506633180574@Atlassian.JIRA>
In-Reply-To: <JIRA.13105867.1506633143000@Atlassian.JIRA>
References: <JIRA.13105867.1506633143000@Atlassian.JIRA> <JIRA.13105867.1506633143563@jira-lw-us.apache.org>
Subject: [jira] [Created] (CASSANDRA-13918) Header only commit logs should
 be filtered before recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 28 Sep 2017 21:13:12 -0000

Blake Eggleston created CASSANDRA-13918:
-------------------------------------------

             Summary: Header only commit logs should be filtered before recovery
                 Key: CASSANDRA-13918
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13918
             Project: Cassandra
          Issue Type: Bug
            Reporter: Blake Eggleston
            Assignee: Blake Eggleston
             Fix For: 3.0.15, 4.0, 3.11.x


Commit log recovery will tolerate commit log truncation in the most recent log file found on disk, but will abort startup if problems are detected in others. 

Since we allocate commit log segments before they're used though, it's possible to get into a state where the last commit log file actually written to is not the same file that was most recently allocated, preventing startup for what should otherwise be allowable incomplete final segments.

Excluding header only files on recovery should prevent this from happening.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org