Docs HomeMongoDB Manual

db.printSecondaryReplicationInfo()

On this page本页内容

Definition定义

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()方法相同。

Output输出

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
Note

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. 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()时,成员可能会在主后面显示负时间值。如果db.printSecondaryReplicationInfo()是在辅助复制一段不活动时间后的写入之后运行的,但在辅助从主接收到具有最新优化的检测信号之前运行的,则会出现这种情况。

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.辅助设备报告的滞后可能不能代表群集运行状况。负值并不表示辅助项领先于主项。

To obtain the most current status for your replica set, run db.printSecondaryReplicationInfo() on the primary.要获得复制副本集的最新状态,请在主服务器上运行db.printSecondaryReplicationInfo()