-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.com/manual/core/replica-set-architectures/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36
*Referrer*: https://docs.mongodb.com/manual/core/replica-set-sync/
*Screen Resolution*: 1920 x 1080
*Location*: https://docs.mongodb.com/manual/core/replica-set-architectures/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 *Referrer*: https://docs.mongodb.com/manual/core/replica-set-sync/ *Screen Resolution*: 1920 x 1080
-
0.25
On this page you recommend three member replica sets.
However earlier on you recommend:
The minimum recommended configuration for a replica set is: A primary, a secondary, and an arbiter. Most deployments, however, will keep three members that store data: A primary and two secondary members.
See https://docs.mongodb.com/manual/core/replica-set-architectures/ for the earlier recommendation.