This version of the documentation is archived and no longer supported.

Adjust Priority for Replica Set Member


The priority settings of replica set members affect the outcomes of elections for primary. Use this setting to ensure that some members are more likely to become primary and that others can never become primary.

The value of the member’s priority setting determines the member’s priority in elections. The higher the number, the higher the priority.


To modify priorities, you update the members array in the replica configuration object. The array index begins with 0. Do not confuse this index value with the value of the replica set member’s _id field in the array.

The value of priority can be any floating point (i.e. decimal) number between 0 and 1000. The default value for the priority field is 1.

To block a member from seeking election as primary, assign it a priority of 0. Hidden members and delayed members have priority set to 0.

For arbiters, the default priority value is 1; however, arbiters cannot become primary regardless of the configured value.

Adjust priority during a scheduled maintenance window. Reconfiguring priority can force the current primary to step down, leading to an election. Before an election the primary closes all open client connections.



Copy the replica set configuration to a variable.

In the mongo shell, use rs.conf() to retrieve the replica set configuration and assign it to a variable. For example:

cfg = rs.conf()

Change each member’s priority value.

Change each member’s priority value, as configured in the members array.

cfg.members[0].priority = 0.5
cfg.members[1].priority = 2
cfg.members[2].priority = 2

This sequence of operations modifies the value of cfg to set the priority for the first three members defined in the members array.


Assign the replica set the new configuration.

Use rs.reconfig() to apply the new configuration.


This operation updates the configuration of the replica set using the configuration defined by the value of cfg.