-
Type:
Bug
-
Resolution: Done
-
Priority:
Critical - P2
-
Affects Version/s: None
-
Labels:
-
Environment:
*Location*: http://docs.mongodb.org/manual/core/replica-set-priority-0-member/
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/core/replica-set-elections/
*Screen Resolution*: 1680 x 1050
*repo*: docs
*source*: core/replica-set-priority-0-member
*Location*: http://docs.mongodb.org/manual/core/replica-set-priority-0-member/ *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/core/replica-set-elections/ *Screen Resolution*: 1680 x 1050 *repo*: docs *source*: core/replica-set-priority-0-member
-
0.25
As of SERVER-14403 write concern majority means majority of voting replica set members.
We should audit the docs to fix-up any examples that imply otherwise (since pre-3.0 all members were used for WC majority calculation.
- has to be finished together with
-
-
- Closed
-