[
https://issues.apache.org/jira/browse/CASSANDRA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803734#action_12803734
]
Jonathan Ellis commented on CASSANDRA-687:
------------------------------------------
+ // (hints are part of the callback and count towards
consistency only under CL.ANY
+ if (consistency_level == ConsistencyLevel.ANY)
+
MessagingService.instance.addCallback(responseHandler,
hintedMessage.getMessageId());
excellent, I like that solution.
+1
> Add ConsistencyLevel.ANY
> ------------------------
>
> Key: CASSANDRA-687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-687
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.6
>
> Attachments: 0001-thrift-changes.patch,
> 0002-add-ConsistencyLevel.ANY-for-writes.patch
>
>
> after CASSANDRA-685, control nodes will throw data away and raise a
> TimeoutException to backpressure clients that are overwhelming the cluster.
> This means we need a ConsistencyLevel "between" ZERO and ONE, meaning that
> Cassandra will block until the data is written *somewhere*, possibly to a HH
> target. (and really we needed this already, judging from people dissatisfied
> with the existing options)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
