cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Schuller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-2338) C* consistency level needs to be pluggable
Date Fri, 18 Mar 2011 00:16:30 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008237#comment-13008237
] 

Peter Schuller commented on CASSANDRA-2338:
-------------------------------------------

I definitely agree that out-of-the-box usability is an important concern, and I never meant
to imply one should complicate the base use-case beyond the current consistency levels. I
also agree about CL.TWO/THREE being questionable (that's why I neer submitted a ticket for
it until hinting that it might be acceptable). That said, I definitely think it would be good
to avoid the need to patch cassandra - something out-of-the-box that allows created configurability
would be nice. Maybe something along the lines of NTS with an API that allows references to
e.g. named custom consistency levels?



> 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

Mime
View raw message