-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Wording around availability zones and multiple-region writes. #123628
base: main
Are you sure you want to change the base?
Conversation
Multiple-region writes don't support strong-consistency. https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels#strong-consistency
@FallenHoot : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit cdae558: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
Any of these three individuals can review this pull request. |
The following reviewer(s) could not be added because they aren't a valid GitHub ID, aren't a valid collaborator on this repo, or are the author of the PR: kanshigtheovankraayany of these three individuals can review this pull request. |
#assign-reviewer:kanshig |
#assign-reviewer:theovankraay |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion. However, I don't quite understand its goal - the wording seems to be saying the same thing, but inverted to focus on multi-region writes, and now communicates less information (there are also single-region write scenarios where AZs add little value, as shown in the table below this sentence). It sounds like a customer was confused, can you articulate how they were confused, and how this wording will clarify for them?
Hi @anaharris-ms, @TheovanKraay, @seesharprun, Normally, in the public repo, a reviewer would merge this PR based on Anastasia's approval above. Is this PR ready to merge, or does Theo's comment need to be addressed first? |
@Court72 Still waiting on some more input here, so not ready to merge yet! Thanks. |
Multi-Region Writes don't support strong consistency, because you can't have an RTO/RPO of zero. Therefore, you can turn availability zones support on for multiple-region writes, but it adds minimal value.
Would need to be verified with PG/PMs if this should be grayed out in the Azure Portal to help with the confusion of this feature.