MongoDB ReplSet Summary
MongoDB replication lag occurs when the secondary node cannot replicate data fast enough to keep up with the rate that data is being written to the primary node. It could be caused by something as simple as network latency, packet loss within your network, or a routing issue.
Operations are classified by legacy wire protocol type (insert, update, and delete only).
This metric can show a correlation with the replication lag value.
Time span between now and last heartbeat from replicaset members.
Count of elections. Usually zero; 1 count by each healthy node will appear in each election. Happens when the primary role changes due to either normal maintenance or trouble events.
Timespan ‘window’ between newest and the oldest op in the Oplog collection.
- Page updated 2020-11-23