[
https://issues.apache.org/jira/browse/CASSANDRA-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Shuler updated CASSANDRA-14769:
---------------------------------------
Fix Version/s: (was: 4.0.x)
4.x
> Batchlog consistency proportional to live nodes, not DC size
> ------------------------------------------------------------
>
> Key: CASSANDRA-14769
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14769
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Batch Log
> Reporter: Benedict Elliott Smith
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Batchlog tries to write to at least two nodes in the DC, if there are two or
> more nodes in the DC. But if all other nodes are down, it will accept
> writing with just CL.ONE. This doesn’t *seem* to be intentional, and I think
> we should probably fail the batch log write in this scenario.
> The prior discussion I could find on this topic was in CASSANDRA-9895,
> wherein the following was stated:
> bq. The idea was that the batchlog should give you the guarantee that you
> won't lose atomicity unless you lose 3 machines during the request
> (coordinator plus two others)
> If this is the intended guarantee, depending on liveness to decide your
> consistency seems busted.
--
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
