[DOCS-6269] Comment on: "manual/core/replica-set-architecture-geographically-distributed.txt" Created: 24/Sep/15  Updated: 30/Oct/23  Resolved: 17/Jan/18

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: Done Votes: 0
Labels: bite-sized, docs-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://docs.mongodb.org/manual/core/replica-set-architecture-geographically-distributed/
User-Agent: Mozilla/5.0 (Linux; Android 4.1.2; GT-I9100 Build/JZO54K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.84 Mobile Safari/537.36
Referrer: http://docs.mongodb.org/manual/core/replica-set-architectures/
Screen Resolution: 320 x 534
repo: docs
source: core/replica-set-architecture-geographically-distributed


Participants:
Days since reply: 6 years, 4 weeks, 1 day ago
Story Points: 0.25

 Description   

This page repeatedly states that priority 0 should be set on nodes in data center 2, 3 etc, but fails to explain WHY this is important. Please clarify this!



 Comments   
Comment by Kay Kim (Inactive) [ 17/Jan/18 ]

The page has been rewritten since the ticket.

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