db.printSecondaryReplicationInfo() output when run on a replica set with two secondary
source: m1.example.net:27002 syncedTo: Mon Mar 01 2021 16:30:50 GMT-0800 (PST) 0 secs (0 hrs) behind the primary source: m2.example.net:27003 syncedTo: Mon Mar 01 2021 16:30:50 GMT-0800 (PST) 0 secs (0 hrs) behind the primary
A member may show a negative time value behind the primary when
is run. This is expected if
db.printSecondaryReplicationInfo() is run after a secondary replicates
a write that follows a period of inactivity, but before the secondary
receives a heartbeat from the primary with the latest optime.
The lag reported by secondaries may not be representative of cluster health. Negative values do not indicate that the secondary is ahead of the primary.
To obtain the most current status for your replica set, run
on the primary.