[
https://issues.apache.org/jira/browse/CASSANDRA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandeep Tata updated CASSANDRA-182:
-----------------------------------
Attachment: CASSANDRA-182.patch
1. Added a class in SequenceFile called SyncWriter
2. New configuration option CommitLogForceLogs if you want "safe" writes. Not
turning this on leaves everything else the same as before. All this does is use
SyncWriter for the logger.
For trunk and 0.4 we should revisit the options we want to allow on the logs,
especially once we re-architect the logger to use batched forces.
> 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
> Affects Versions: trunk, 0.3
> Reporter: Sandeep Tata
> Assignee: Sandeep Tata
> Fix For: trunk, 0.3
>
> 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.
