-
Type:
Bug
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Cloud Manager, Ops Manager
-
Labels:
-
Environment:
*Location*: https://docs.cloud.mongodb.com/tutorial/edit-replica-set/#remove-a-replica-set-member
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36
*Referrer*: https://jira.mongodb.org/browse/HELP-2018
*Screen Resolution*: 1440 x 900
*repo*: REPONAME
*source*: tutorial/edit-replica-set
*Location*: https://docs.cloud.mongodb.com/tutorial/edit-replica-set/#remove-a-replica-set-member *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.86 Safari/537.36 *Referrer*: https://jira.mongodb.org/browse/HELP-2018 *Screen Resolution*: 1440 x 900 *repo*: REPONAME *source*: tutorial/edit-replica-set
-
0.5
When removing a member of a replica set, this page says that you need to retain a majority of the members of the original replica set. That sentence is wrong or misleading, since after removing a member, you have a new "original replica set", and you need a majority of that replica set to maintain writability.
- links to