[DOCS-6889] Comment on: "manual/tutorial/deploy-geographically-distributed-replica-set.txt" Created: 30/Dec/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: bite-sized, docs-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.org/v3.0/tutorial/deploy-geographically-distributed-replica-set/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.3.0
Screen Resolution: 1080 x 675
repo: docs
source: tutorial/deploy-geographically-distributed-replica-set


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

A user on IRC suggested that this document (considering the 3 nodes example) includes reasoning as to why having a single node in site B actually provides a geographically redundant set. The node in site B can for example never become a primary node - and hence not being fully redundant.

It could also benefit from updates (or a link to) as to how to really make a data centre geographic set-up work - and the only way (As far as I know) to do that, is by using at least one node in a tertiary data centre.

Reporter: Derick



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

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