MongoDB Error 216: Replica Set Election Active

Replica set elections are a normal part of MongoDB's high availability. They occur when the primary node becomes unavailable (e.g., due to network issues, restarts, or crashes). The remaining secondaries hold an election to choose a new primary. This process typically takes a short amount of time (seconds to a few minutes).

text

Monitor the replica set status to confirm the election has concluded and a new primary has been elected.

db.replicaSetStatus().state

Once the election is complete, your application should be able to connect to the new primary without further intervention.

text

The 'Election In Progress' error can be triggered if replica set members cannot communicate effectively, preventing a stable election. Log in to each replica set member and check network connectivity.

ping <hostname_of_other_member>

Verify that the MongoDB ports (default 27017) are open and accessible between all members. Use `telnet` or `nc` to test port connectivity.

telnet <hostname_of_other_member> 27017

Review MongoDB logs on all members for any network-related errors or connection refused messages. Ensure the `net.bindIp` configuration correctly allows connections from other replica set members.

text

If network issues are identified, resolve them by adjusting firewall rules, ensuring correct DNS resolution, or correcting `net.bindIp` in the `mongod.conf` file.

text

If elections are happening frequently or taking too long, the primary node might be experiencing issues. Connect to the primary (if accessible) or a secondary and check its health.

db.serverStatus()

Examine the `connections` and `network` sections of `serverStatus` for any anomalies, such as excessive connections or high network traffic. Also, check the `globalLock` for any indications of prolonged lock contention.

text

Review the MongoDB logs on the primary for any errors related to disk I/O, memory, or application-level issues that might be causing it to become unresponsive or crash.

text

If the primary is consistently unhealthy, consider restarting it gracefully. If the issue persists, investigate the underlying cause (e.g., resource exhaustion, problematic queries, or hardware problems) and address it. In severe cases, you might need to initiate a manual failover.

text

Incorrect replica set configuration can lead to election instability. Connect to any member of the replica set and run `rs.conf()` to view the current configuration.

rs.conf()

Carefully review the `members` array in the configuration. Ensure that all hostnames and ports are accurate, and that each member is correctly identified with its `_id` and `host`.

text

Check the `priority` settings. A priority of 0 means a member cannot be elected primary. Ensure at least one member has a non-zero priority. Also, verify `votes` are correctly assigned.

text

If the configuration is incorrect, use `rs.reconfig()` to update it. **Caution:** Incorrectly reconfiguring a replica set can lead to data loss or downtime. Always back up your configuration before making changes.

rs.reconfig(newConfig, { force: true })