[DOCS-10172] Atlas Replication Factor and Availability Zones Created: 25/Apr/17  Updated: 17/May/17  Resolved: 17/May/17

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Luke Phillippi Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 6 years, 39 weeks, 1 day ago

 Description   

In step 2 of the Scaling an Existing Cluster procedure within the Atlas documentation, the table states the following:

Replication Factor You can change the number of members in your cluster’s replica set. The replica set spans a minimum of three availability zones, and each member of the replica set runs on a separate instance. [...]

However, Atlas now also supports deploying clusters into regions that only contain two availability zones; the documentation should be updated to reflect this.



 Comments   
Comment by Ravind Kumar (Inactive) [ 17/May/17 ]

Merged: https://github.com/10gen/cloud-docs/commit/1ff9d4e3b3ae896e58c48fa458dc4dc0d726285f

Comment by Ravind Kumar (Inactive) [ 26/Apr/17 ]

andrew.davidson if there are no objections, I'm also going to change the following FAQ line item:

Will you support more regions in the future?

with

"What AWS Regions does Atlas support?"

"Atlas supports all AWS regions.

Atlas marks AWS regions that support at least three availability zones as Recommended, as they provide higher availability over other zones. Other AWS regions support only two availability zones, but may be preferred if latency or location is a priority. See Amazon Availability Zones for more information.
"

Thanks.

Generated at Thu Feb 08 07:59:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.