We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I would like to report an issue on page https://opensource.docs.scylladb.com/branch-5.4/cql/consistency-calculator
How is it possible that e.g, with Nodes=3, RF=3,
It is true that the later has lower availability since losing a node will return an error, but a successful read will always be consistent.
READ_CL=ALL should always guarantee consistent reads for any WRITE_CL != ANY
The text was updated successfully, but these errors were encountered:
@tgrabiec am I hallucinating? :)
Sorry, something went wrong.
I think you're right, {READ_CL=ALL, WRITE_CL=QUORUM} should be consistent, since the read set always overlaps with any past write set.
tzach
No branches or pull requests
I would like to report an issue on page https://opensource.docs.scylladb.com/branch-5.4/cql/consistency-calculator
Problem
How is it possible that e.g, with Nodes=3, RF=3,
It is true that the later has lower availability since losing a node will return an error, but a successful read will always be consistent.
Suggest a fix
READ_CL=ALL should always guarantee consistent reads for any WRITE_CL != ANY
The text was updated successfully, but these errors were encountered: