Wording around availability zones and multiple-region writes.
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.
@FallenHoot : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit cdae558:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/reliability/reliability-cosmos-db-nosql.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@anaharris-ms
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
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
@fallenhoot
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.
Without hearing anything back, I need to recommend that we close this PR as unresolved.
#please-close