[DOCS-14316] Add a note for Availability Zones on Replica Set deployment Page Created: 26/Mar/21 Updated: 08/Jan/24 Resolved: 15/Dec/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0, 5.0.0, 6.0.0, 7.1.0, 7.0.0, 7.2.0, 7.3.0, Server_Docs_[20240108] |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Adamo Tonete (Inactive) | Assignee: | Jason Price |
| Resolution: | Done | Votes: | 0 |
| Labels: | quick-win, replication, request, server-docs-bug-bash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 8 weeks, 5 days ago |
| Story Points: | 2 |
| Description |
DescriptionAs a suggestion, in the page: https://docs.mongodb.com/manual/core/replica-set-architecture-geographically-distributed/ We are referring to DC1 and DC2 however cloud providers has the concept of availability zones. Which are the same "DC" A replica set deployment in a single DC can offer high availability if all the instances are in the same DC but in different availability zones as it is very unlikely to all the AZ to fail.
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Jason Price [ 08/Dec/23 ] |