Consistency level #710
Merged
Consistency level #710
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
amnonh
force-pushed
the
consistency_level
branch
from
5b174c6 to
bbc1279
Compare
|
|
|
Why ALL and ANY? |
|
Both are potential problems, see the description
…On Thursday, August 15, 2019, Tzach Livyatan ***@***.***> wrote:
Why ALL and ANY?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#710?email_source=notifications&email_token=AAQFDP7WJBHHHVYEW7VL5U3QEWI7JA5CNFSM4IJWAV42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4MQBBA#issuecomment-521732228>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQFDP6JOPGFMAHFQXZQOZTQEWI7JANCNFSM4IJWAV4Q>
.
|
|
@slivne ping |
|
All and Any are needed - the text around them should be added to make it
clear they are "problematic" and should not be used.
I also want to see the LOCAL_ONE vs ONE / LOCAL_QUORUM vs QUORUM - it is
relevant for multi-dc clusters (mainly) - or users that want to add another
DC and may not be aware that they will be running into issues.
QUORUM is obvious ...
non obvious example:
- LOCAL_ONE means only in this DC
- ONE can cause queries to be sent to another DC (especially with
heatweighted load balancing).
…On Sun, Aug 18, 2019 at 11:49 AM Amnon Heiman ***@***.***> wrote:
@slivne <https://github.com/slivne> ping
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#710?email_source=notifications&email_token=AA2OCCGXNUA2Z7EJ73KO7TLQFEEHXA5CNFSM4IJWAV42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4Q3PYQ#issuecomment-522303458>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2OCCFWJJ3UOC7B73L5NC3QFEEHXANCNFSM4IJWAV4Q>
.
|
amnonh
force-pushed
the
consistency_level
branch
2 times, most recently
from
7c9a91d to
aa180c8
Compare
|
|
slivne
suggested changes
Sep 1, 2019
| "panels": [ | ||
| { | ||
| "class": "gauge_errors_panel", | ||
| "description": "Using consistency level ANY in a query will hurt persistency, if the node receiving the request will fail the data may be lost", |
| }, | ||
| { | ||
| "class": "gauge_errors_panel", | ||
| "description": "Using consistency level ALL in a query will hurt availability, if the node is unavailable operations will fail", |
There was a problem hiding this comment.
"if the node is unavailable operations will fail" --> "if a node is unavailable operations will fail",
| "panels": [ | ||
| { | ||
| "class": "gauge_errors_panel", | ||
| "description": "Using consistency level ONE in a query when there is more than one DC will hurt performance, queries may end in the non-local DC. Use Local-One instead", |
There was a problem hiding this comment.
"Using consistency level ONE in a query when there is more than one DC will hurt performance, queries may end in the non-local DC. Use Local-One instead" -->
"Using consistency level ONE in a query when there is more than one DC may hurt performance, queries may end up in the non-local DC. Use LOCAL_ONE instead"
| }, | ||
| { | ||
| "class": "gauge_errors_panel", | ||
| "description": "Using consistency level QUORUM in a query when there is more than one DC will hurt performance, queries may end in the non-local DC. Use Local-QUORUM instead", |
There was a problem hiding this comment.
"Using consistency level QUORUM in a query when there is more than one DC will hurt performance, queries may end in the non-local DC. Use Local-QUORUM instead"
-->
"Using consistency level QUORUM in a query when there is more than one DC may hurt performance, queries may end up in the non-local DC. Use LOCAL_QUORUM instead"
Add a graph for ANY and ALL and a cross-dc section
Add a graph for ANY and ALL and a cross-dc section
Add a graph for ANY and ALL and a cross-dc section
amnonh
force-pushed
the
consistency_level
branch
from
aa180c8 to
83b304b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #706
Fixes #579