[
https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008164#comment-13008164
]
Matthew F. Dennis commented on CASSANDRA-2338:
----------------------------------------------
That's a good point and I can certainly see the value in that, but that doesn't
really have anything to do with how I'm writing the data. Lets say I do have
an ETL cluster and then when I'm writing to my operational cluster I want to
ensure that at least one copy of the data exists in my ETL cluster AND that I
have a local quorum in operational cluster for consistency purposes before
returning to the client.
> C* consistency level needs to be pluggable
> ------------------------------------------
>
> Key: CASSANDRA-2338
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2338
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Matthew F. Dennis
> Priority: Minor
>
> for cases where people want to run C* across multiple DCs for disaster
> recovery et cetera where normal operations only happen in the first DC (e.g.
> no writes/reads happen in the remove DC under normal operation) neither
> LOCAL_QUORUM or EACH_QUORUM really suffices.
> Consider the case with RF of DC1:3 DC2:2
> LOCAL_QUORUM doesn't provide any guarantee that data is in the remote DC.
> EACH_QUORUM requires that both nodes in the remote DC are up.
> It would be useful in some situations to be able to specify a strategy where
> LOCAL_QUORUM is used for the local DC and at least one in a remote DC (and/or
> at least in *each* remote DC).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
