[
https://issues.apache.org/jira/browse/CASSANDRA-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923609#action_12923609
]
Jonathan Ellis commented on CASSANDRA-1644:
-------------------------------------------
As the comment says:
+ // we used to try to avoid instantiating commitlog (thus
creating an empty segment ready for writes)
+ // until after recover was finished. this turns out to be
fragile; it is less error-prone to go
+ // ahead and allow writes before recover(), and just skip
active segments when we do.
> Commitlog.recover can delete the commitlog segment instance() just created
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-1644
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1644
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Blocker
> Fix For: 0.7.0
>
> Attachments: 1644.txt
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
