Navigation

Replica Set Has No Primary

Description

At time T, no primary was detected in replica set ABC.

Common Triggers

  • The workload exceeds the cluster’s throughput limits and compute resources.
  • A network issue with the cloud provider is preventing voting members of the replica set from communicating with each other, such that a primary cannot be elected.

Possible Solutions

  • Check the cluster’s metrics to determine if there are sufficient compute resources for your workload.
    • If the cluster is exhausting CPU, disk IOPS, connections, or other resources, upgrade to a cluster tier and instance size that supports your workload.
    • If the cluster’s metrics are normal, there could be a network issue with the cloud provider. Atlas automatically attempts to repair these issues. If the problem persists, contact MongoDB Support.

For more information on the alert condition, see Replica set has no primary.