[Cassandra] Safer consistency settings #9171
Merged
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.
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