[
https://issues.apache.org/jira/browse/CASSANDRA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711775#action_12711775
]
Jonathan Ellis commented on CASSANDRA-182:
------------------------------------------
Assuming we don't hear back from Avinash & Prashant, I suggest that we include
a "known issues" section in the README for 0.3 noting this problem. I'm not
comfortable with basing the CL on brand-new code.
For 0.4 let's take a closer look at FastSync and either build on that or rip it
out and go with the approach in your patch (either in CL or the writer). I'd
like to see this coupled with a CL executor that force()s less than once per
mutation if there is a constant stream of writes, similar to postgresql's
commit_delay setting
(http://www.postgresql.org/docs/8.3/static/runtime-config-wal.html).
> 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.
