You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/01/19 16:48:54 UTC

[jira] Assigned: (CASSANDRA-687) Add ConsistencyLevel.ANY

     [ https://issues.apache.org/jira/browse/CASSANDRA-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis reassigned CASSANDRA-687:
----------------------------------------

    Assignee: Gary Dusbabek  (was: Jonathan Ellis)

> 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
>
>
> 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.