On this page本页内容
db.printSecondaryReplicationInfo() Prints a formatted report of the replica set status from the perspective of the secondary member of the set. 从副本集secondary成员的角度打印副本集状态的格式化报告。The output is identical to the 输出与rs.printSecondaryReplicationInfo() method.rs.printSecondaryReplicationInfo()方法相同。
Example 在具有两个辅助成员的副本集上运行时的db.printSecondaryReplicationInfo() output when run on a replica set with two secondary members:db.printSecondaryReplicationInfo()输出示例：
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
The 在db.printSecondaryReplicationInfo() method run in mongosh does not return JSON. mongosh中运行的db.printSecondaryReplicationInfo()方法不返回JSON。Use 使用db.printSecondaryReplicationInfo() for manual inspection, and rs.status() in scripts.db.printSecondaryReplicationInfo()进行手动检查，并在脚本中使用rs.status()。
A delayed member may show as 当主成员上的非活动时段大于0 seconds behind the primary when the inactivity period on the primary is greater than the members[n].secondaryDelaySecs value.members[n].secondaryDelaySecs值时，延迟成员可能会显示为比主成员晚0秒。
A member may show a negative time value behind the primary when 当运行db.printSecondaryReplicationInfo() is run. db.printSecondaryReplicationInfo()时，成员可能会在主对象后面显示负时间值。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.db.printSecondaryReplicationInfo()在辅助服务器复制了一段非活动时间后的写入之后运行，但在辅助服务器接收到来自主服务器的具有最新优化的心跳之前运行，则会出现这种情况。
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 要获取副本集的最新状态，请在主服务器上运行db.printSecondaryReplicationInfo() on the primary.db.printSecondaryReplicationInfo()。