[
https://issues.apache.org/jira/browse/CASSANDRA-16773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17372054#comment-17372054
]
Dan Sarisky commented on CASSANDRA-16773:
-----------------------------------------
So, I recognize that 8119 would solve this. 8119 is also a lot more complex.
As well as being 6 plus years old and going nowhere. Is a more targeted
consistency level change acceptable?
> Consistency Level ALL_MINUS_ONE
> -------------------------------
>
> Key: CASSANDRA-16773
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16773
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Coordination
> Reporter: Dan Sarisky
> Priority: Normal
>
> We have an application that is deployed in a variety of Cassandra cluster
> configurations using RF=3. We'd like to be able to always tolerate a single
> node being down. We write data into the cluster using consistency level TWO.
> We would like to add ConsistencyLevel.ALL_MINUS_ONE to more clearly express
> our desire for relatively strong consistency. EACH_QUORUM is not enough but
> CL.ALL has unacceptable availability.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
