You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Edward Capriolo (JIRA)" <ji...@apache.org> on 2011/03/17 22:28:29 UTC
[jira] Commented: (CASSANDRA-2338) C* consistency level needs to be
pluggable
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008147#comment-13008147 ]
Edward Capriolo commented on CASSANDRA-2338:
--------------------------------------------
I was thinking that the approach to the other data centers is allow the CF information to be overridden per host but still stored across the cluster. For example if I have an ETL cluster. I only want those nodes to have read_repair_chance=0.
> 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