Details
-
Improvement
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
Referring to http://docs.mongodb.org/manual/administration/replica-sets/#secondary-only-members
The example sets the members[0] node's priority to 0. Unfortunately, the 0th node is often the primary. Changing the primary's priority to 0 is not possible at the moment, see SERVER-3815.
I suggest to reverse the order of priorities in the example, so that the 0th node has the highest priority, to reduce the chance that users run into this problem. The explanation below would have to be changed as well.
In addition, I'd mention (in a warning box) that the current primary's priority cannot be changed to 0 without stepping the node down first.
Attachments
Issue Links
- is related to
-
SERVER-3815 replica sets: can't set priority of current primary to zero
-
- Closed
-