[
https://issues.apache.org/jira/browse/CASSANDRA-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291265#comment-15291265
]
Benjamin Lerer commented on CASSANDRA-11743:
--------------------------------------------
||Branch||utests||dtests||
|[2.2|https://github.com/blerer/cassandra/tree/11743-2.2]|[2.2|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-2.2-testall/]|[2.2|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-2.2-dtest/]|
|[3.0|https://github.com/blerer/cassandra/tree/11743-3.0]|[3.0|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-3.0-testall/]|[3.0|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-3.0-dtest/]|
|[3.7|https://github.com/blerer/cassandra/tree/11743-3.7]|[3.7|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-3.7-testall/]|[3.7|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11743-3.7-dtest/]|
The new patch does as suggested.
> 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)
