Navigation
This is an upcoming (i.e. in progress) version of the manual.

rs.printSlaveReplicationInfo()

On this page

Definition

rs.printSlaveReplicationInfo()

Returns a formatted report of the status of a replica set from the perspective of the secondary member of the set. The output is identical to that of db.printSlaveReplicationInfo().

Output

The following is example output from the rs.printSlaveReplicationInfo() method issued on a replica set with two secondary members:

source: m1.example.net:27017
    syncedTo: Thu Apr 10 2014 10:27:47 GMT-0400 (EDT)
    0 secs (0 hrs) behind the primary
source: m2.example.net:27017
    syncedTo: Thu Apr 10 2014 10:27:47 GMT-0400 (EDT)
    0 secs (0 hrs) behind the primary

A delayed member may show as 0 seconds behind the primary when the inactivity period on the primary is greater than the members[n].slaveDelay value.

A member may show a negative time value behind the primary when rs.printSlaveReplicationInfo() is called. This behavior is expected if the method is called after a secondary replicates a write following a period of inactivity, but before it has received a heartbeat from the primary with its latest optime.

Note

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.

For the most up-to-date information on your replica set, it is generally advisable to run rs.printSlaveReplicationInfo() on the primary.