[jira] Commented: (CASSANDRA-399) Consisteny Level of ZERO blocks for ack on Commit Log

["Sandeep Tata (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749195#action_12749195 ] 

Sandeep Tata commented on CASSANDRA-399:
----------------------------------------

I remember we put this in to get limited read-your-writes consistency for a session. (Log + rm.apply()  before ack.)
See CASSANDRA-132.

There are cases when this is not the right thing to do (eg skip logging during a load operation), but for a normal client, read-your-writes is way easier to deal with than pure eventual consistency. 







> Consisteny Level of ZERO blocks for ack on Commit Log
> -----------------------------------------------------
>
>                 Key: CASSANDRA-399
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-399
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.4
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.4
>
>         Attachments: 0001-CASSANDRA-399-If-consistency-level-is-set-to-ZERO-an.patch
>
>
> If consistency level is set to ZERO and endpoint is local, clients must wait for a write to the commit log. We need to remove this special case, and just send through MessagingService.getMessagingInstance().sendOneWay.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.