[
https://issues.apache.org/jira/browse/CASSANDRA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-182:
-------------------------------------
Attachment: 0007-arrayblockingqueue.txt
0006-config-options.txt
0005-custom-CommitLogExecutorService-that-can-fsync-per-mul.txt
0004-threadpoolexecutor.txt
0003-naive-fsync-after-each-log-entry.txt
0002-mv-AbstractWriter-to-its-own-top-level-class-and-remov.txt
0001-CASSANDRA-182-handle-incomplete-CL-entries-on-recover.txt
> 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:
> 0001-CASSANDRA-182-handle-incomplete-CL-entries-on-recover.txt,
> 0002-mv-AbstractWriter-to-its-own-top-level-class-and-remov.txt,
> 0003-naive-fsync-after-each-log-entry.txt, 0004-threadpoolexecutor.txt,
> 0005-custom-CommitLogExecutorService-that-can-fsync-per-mul.txt,
> 0006-config-options.txt, 0007-arrayblockingqueue.txt, 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.
