[ https://issues.apache.org/jira/browse/CASSANDRA-11743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Lerer updated CASSANDRA-11743: --------------------------------------- Resolution: Fixed Status: Resolved (was: Ready to Commit) Committed into 2.2 at 6add3c9acc063005198510e9627ae9e783e54e91 and merged into 3.0, 3.7 and trunk > 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 > > Attachments: 11743-2.2.txt > > > 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)