You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matthew F. Dennis (JIRA)" <ji...@apache.org> on 2011/03/16 04:34:29 UTC
[jira] Created: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
---------------------------------------------------------
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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
Posted by "Peter Schuller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007380#comment-13007380 ]
Peter Schuller commented on CASSANDRA-2338:
-------------------------------------------
I think this highlights even better than CASSANDRA-2013 that there is at least interest (if not need) to be able to specify with finer granularity what your requirements are. One can probably come up with a list of 15 cases and suddenly ConsistencyLevel is a huge beast. A few seemingly reasonable/realistic situations I can think of:
* Your situation, except there are 3 DC:s, 2 of which are production and one analysis. Now you want LOCAL_QUORUM_PLUS_ONE_IN_THIS_OTHER_PARTICULAR_REMOTE_DC
* You may want the reverse of requiring additional replicas; e.g., "reads shall never try to go beyond the local DC; I prefer failures/timeouts)"
* Maybe you one one replicate per DC, but no QUOROM in each.
It would be a bigger API change, and a more invasive code change. The simplest way to do this I can think of, is to allow the passing of a "ReplicaSelectionPolicy" (for lack of a better word right now) which allows you to specify, globally and on a per-dc level (assuming dc:s are named):
(1) How many replicates are *allowed* to be consulted.
(2) How many replicas are *required* to be consulted.
(1) would be of interest for reads, and (2) for both reads and writes.
Is this complete overkill?
> C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
> ---------------------------------------------------------
>
> 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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2338) C* consistency level needs to be
pluggable
Posted by "Edward Capriolo (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007530#comment-13007530 ]
Eric Evans commented on CASSANDRA-2338:
---------------------------------------
AIUI, the reasoning behind the ConsistencyLevel enum was to simply things, to codify best practice and make it easier for people to understand and do the Right Thing. In other words, sacrifice some flexibility in exchange for usability. For this to work, the Right Answer in situations like this is to tweak the RF knob to work with the available consistency options.
If consensus is that this trade-off is wrong (usability vs flexibility), then the reasonable thing to do is eliminate ConsistencyLevel in favor of an int.
LOCAL_QUORUM_PLUS_ONE_REMOTE is a Bad Idea IMO, so is TWO and THREE.
> C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
> ---------------------------------------------------------
>
> 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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007548#comment-13007548 ]
Jonathan Ellis commented on CASSANDRA-2338:
-------------------------------------------
An int doesn't capture enough information though, it's just "the first nodes that reply" which isn't always what you want.
IMO we should ship commonly-used levels (which probably doesn't include TWO or THREE) but make it pluggable so people can add custom ones.
> C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
> ---------------------------------------------------------
>
> 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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2338) C* consistency level needs to
be pluggable
Posted by "Peter Schuller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019088#comment-13019088 ]
Peter Schuller commented on CASSANDRA-2338:
-------------------------------------------
A related concern that is not directly about consistency but about performance is that one may wish to control to what extent requests are sent to "extra" nodes than required by consistency.
For example, a very nice property of running with QUORUM + read-repair turned fully on (and let's say RF=3), is that for any request, it's totally fine for a single node to be e.g. slow without giving an application visible poor latency. If the dynamic snitch is engaged, the slow node should usually not be the one that is considered closest, so it's not the one getting the data read.
Turning off read-repair negates that since without read repair, messages are sent only to those required by consistency level. So if any node is slow, the request will be slow.
Also related is that for reads that are expected to be small, it may be that it is irrelevant to do the digest-only optimization. For many cases, the disk I/O and perhaps CPU cost is going to be a lot more relevant than the overhead of sending some extra ~ 40 bytes or whatever over the network. In such cases, it is probably often preferable to send read commands to all, or at least multiple, nodes such one is not depending on a specific node being up + fast in order to return the data.
For example, suppose I have a low-consistency situation where I care about good latency in terms of avoiding outliers. While CL.ONE is the typical suggestion, a better avoidance of outliers should be possible if CL.ONE is used but each node is sent a full read command such that the request can complete immediately whenever any node responds, without waiting for a timeout (or just a slow response not timing out) from the node that happens to be considered closest.
This may be out of scope for this ticket, but maybe worth at least thinking about. If Cassandra can offer, at reasonable complexity for the application writer, detailed choices for all of these at the same time:
(1) Least number of endpoints for consistency, at a per-DC level (to control consistency).
(2) Maximum allowed, at a per-DC level (to control latency).
(3) Pessimistic "over-messaging" (to control latency, in particular outliers).
... it should be enough to cover a great many cases (and from a PR perspective, under the assumption that the complexity cost is not too high, it would really show-case what kind of detailed control and specific tuning is fundamentally possible given the data and messaging model).
> 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
[jira] Commented: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
Posted by "Matthew F. Dennis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007615#comment-13007615 ]
Matthew F. Dennis commented on CASSANDRA-2338:
----------------------------------------------
two of the most common requests I hear from users is specify an arbitrary number of replicas (usually two) and specify things like (at least one copy in one other DC).
In any case, I certainly wasn't trying tp advocate that LOCAL_QUORUM_PLUS_ONE_REMOTE be the only one (even though the bug came out sounding like that); it's just one of many examples of more complex scenarios that I've seen several requests for.
Making it pluggable is certainly the best long term choice. As people develop ones that are generally useful and well written, we can just include them.
> C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
> ---------------------------------------------------------
>
> 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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CASSANDRA-2338) C* consistency level needs to
be pluggable
Posted by "David Strauss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13457563#comment-13457563 ]
David Strauss commented on CASSANDRA-2338:
------------------------------------------
Just chiming in with another use case: first data found. We have a large CF indexed by the hash of what's in the row. Basically, any non-empty result is guaranteed to be the same. The common case is for all replicas to be up-to-date, so CL.ONE is almost ideal. But, we also write with CL.ONE, and that means we only have eventually consistent read-after-write. A pluggable CL would allow something more ideal.
The ideal would be:
1. Send read to all replicas.
2. On the first non-NotFoundException response, we're done.
3. If all replicas return NotFoundException, then it truly doesn't exist.
CL.ONE just goes with the NotFoundException if it's the first response. CL.ALL waits for all responses, even if the first one is all we need.
This may be useful in the reverse, too:
1. Send read to all replicas.
2. On the first NotFoundException response, we're done.
3. If all replicas return data, then use the one with the latest timestamp.
I also second Peter's request for controlling what extent requests get sent to all replicas on reads. In our case, it's usually okay to wait a bit longer but only put I/O load on one out of all the replica boxes. This map well to the algorithms above in higher-latency scenarios.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CASSANDRA-2338) C* needs a
LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007609#comment-13007609 ]
Eric Evans commented on CASSANDRA-2338:
---------------------------------------
bq. An int doesn't capture enough information though, it's just "the first nodes that reply" which isn't always what you want.
Right, I was using "int" to mean "arbitrary", as opposed to picking from a fixed set (and I wasn't advocating that approach :)).
bq. IMO we should ship commonly-used levels (which probably doesn't include TWO or THREE) but make it pluggable so people can add custom ones.
This is a much better alternative IMO.
> C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level
> ---------------------------------------------------------
>
> 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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CASSANDRA-2338) C* consistency level needs to be
pluggable
Posted by "Matthew F. Dennis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew F. Dennis updated CASSANDRA-2338:
-----------------------------------------
Description:
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).
was:
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 LOCAL_QUORUM (for local consistency) + "at least one remote" for durability/disaster proofing.
Summary: C* consistency level needs to be pluggable (was: C* needs a LOCAL_QUORUM_PLUS_ONE_REMOTE consistency level)
> 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
[jira] Commented: (CASSANDRA-2338) C* consistency level needs to be
pluggable
Posted by "Matthew F. Dennis (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (CASSANDRA-2338) C* consistency level needs to be
pluggable
Posted by "Brandon Williams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008189#comment-13008189 ]
Brandon Williams commented on CASSANDRA-2338:
---------------------------------------------
And when your ETL cluster is unavailable, your whole app is dead?
> 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
[jira] Commented: (CASSANDRA-2338) C* consistency level needs to be
pluggable
Posted by "Peter Schuller (JIRA)" <ji...@apache.org>.
[ 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