You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2016/05/17 13:47:12 UTC
[jira] [Comment Edited] (CASSANDRA-11743) Race condition in
CommitLog.recover can prevent startup
[ https://issues.apache.org/jira/browse/CASSANDRA-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286641#comment-15286641 ]
Benjamin Lerer edited comment on CASSANDRA-11743 at 5/17/16 1:46 PM:
---------------------------------------------------------------------
[~blambov] could you review?
was (Author: blerer):
[~blambov]
> 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.1.x, 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)