Skip to content
New issue

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

[Cassandra] Safer consistency settings #9171

Merged
merged 1 commit into from
Oct 15, 2024
Merged

Conversation

rkargMsft
Copy link
Contributor

@rkargMsft rkargMsft commented Oct 11, 2024

While the EACH_QUORUM/LOCAL_QUORUM is correct for consistency and does provider a faster read, it also will make it impossible to write if a single data center is unreachable.

For example, a Cassandra cluster across three data centers would need to be able to have each individual data center achieve it's own quorum for the write to be successful.
With using QUORUM/QUORUM for write/read, there only needs to be a single quorum across the whole cluster. If an entire data center in the three DC scenario is unreachable, then you can still have a Quorum from nodes in the reachable two data centers to complete a write.

The EACH_QUORUM for writes seems like it's more dangerous than the equally consistent QUORUM/QUORUM settings.

Microsoft Reviewers: Open in CodeFlow

@ReubenBond ReubenBond merged commit 92c6785 into dotnet:main Oct 15, 2024
22 checks passed
@rkargMsft rkargMsft deleted the quorum branch October 16, 2024 19:20
@github-actions github-actions bot locked and limited conversation to collaborators Nov 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants