[
https://issues.apache.org/jira/browse/CASSANDRA-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-399.
--------------------------------------
Resolution: Fixed
Committed before I saw Sandeep's objection. But insert -- the method that
handles ConsistencyLevel.ZERO -- is the wrong place to do this. If you want
any blocking you need to use ONE or higher, that's how it's supposed to work.
> 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.
