[
https://issues.apache.org/jira/browse/CASSANDRA-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-1780:
--------------------------------------
Attachment: 1780.txt
Having written this I'm not sure if it's all that useful since in periodic mode
we don't block for the commitlog append (and don't even set up the callback
hooks to do that in the PeriodicCommitLogExecutorService, which is one of the
reasons it's faster). Still, if the performance impact is negligible (as
mdennis tested a few months ago) it could be worth making it the default.
> periodic + flush commitlog mode
> -------------------------------
>
> Key: CASSANDRA-1780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1780
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: 1780.txt
>
>
> periodic-sync commitlog mode only flushes before it syncs, which means its
> best case durability is very similar to its worst case. if we had a mode
> that flushed but did not sync then it would only lose data for actual power
> failures.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
