[
https://issues.apache.org/jira/browse/CASSANDRA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749206#action_12749206
]
Sandeep Tata commented on CASSANDRA-399:
----------------------------------------
I'm +1 on the patch, but we should re-open 132.
Current insertBlocking=1 is not the same as session level read-your-writes.
I guess we could just special-case this write for insertBlocking=1. I'd rather
not introduce a new ConsistencyLevel.
ConsistencyLevel.ZERO should help stress test MessagingService... I remember
with the old codepath writes would get queued up in the MessagingService and we
ended up with a few lost writes. Should be interesting to see if those problems
pop up again.
> 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.
