[
https://issues.apache.org/jira/browse/CASSANDRA-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935848#action_12935848
]
Peter Schuller commented on CASSANDRA-1780:
-------------------------------------------
Does not this behavior imply that batch mutations are actually *not* atomic
when running in periodic commit mode? I.e., if memtables receive data that in
the face of a crash are lost, you may see the partial results of a batch mutate
that then go away and never ever come back.
(Atomicity (but not isolation) has been claimed a few times on the ML:s for
updates within a single row.)
> 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.
