Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 19 May 2016 15:16:12 +0000 (UTC)
From: "Benjamin Lerer (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12966757.1462890073000.236849.1463670972881@Atlassian.JIRA>
In-Reply-To: <JIRA.12966757.1462890073000@Atlassian.JIRA>
References: <JIRA.12966757.1462890073000@Atlassian.JIRA> <JIRA.12966757.1462890073785@arcas>
Subject: [jira] [Updated] (CASSANDRA-11743) Race condition in
 CommitLog.recover can prevent startup
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 19 May 2016 15:16:14 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-11743:
---------------------------------------
    Reviewer: Branimir Lambov

> Race condition in CommitLog.recover can prevent startup
> -------------------------------------------------------
>
>                 Key: CASSANDRA-11743
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11743
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Lifecycle
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>             Fix For: 2.2.x, 3.0.x, 3.x
>
>
> In {{CommitLog::recover}} the list of segments to recover from is determined by removing the files managed by the {{CommitLogSegmentManager}} from the list of files present in the commit log directory. Unfortunatly, due to the way the creation of segments is done there is a time window where a segment file has been created but has not been added yet to the list of segments managed by the {{CommitLogSegmentManager}}. If the filtering ocurs during that time window the Commit log might try to recover from that new segment and crash.   


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)