[
https://issues.apache.org/jira/browse/CASSANDRA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733998#action_12733998
]
Sandeep Tata commented on CASSANDRA-182:
----------------------------------------
I did figure how to avoid using force(true) to flush the metadata in addition
to the data (2 disk forces instead of one). If you preallocate the pages for
the log file, you need to force(true) only when you have to grab more pages for
the log. This would of course require some extra work in the logger code so the
end of the log can be tracked without depending on file size/end of file.
> CommitLog.add doesn't really force to disk
> ------------------------------------------
>
> Key: CASSANDRA-182
> URL: https://issues.apache.org/jira/browse/CASSANDRA-182
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.3
> Reporter: Sandeep Tata
> Assignee: Jonathan Ellis
> Fix For: 0.4
>
> Attachments: CASSANDRA-182.patch
>
>
> CommitLog.add does't really force writes to disk. This could result in acked
> writes being lost.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
