rs.printSecondaryReplicationInfo()
On this page本页内容
Definition定义
rs.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输出与db.printSecondaryReplicationInfo()
.db.printSecondaryReplicationInfo()
相同。
Output输出
Example 示例rs.printSecondaryReplicationInfo()
output when run on a replica set with two secondary members:rs.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 在rs.printSecondaryReplicationInfo()
method run in mongosh
does not return JSON. mongosh
中运行的rs.printSecondaryReplicationInfo()
方法不返回JSON。Use 使用rs.printSecondaryReplicationInfo()
for manual inspection, and rs.status()
in scripts.rs.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 当运行rs.printSecondaryReplicationInfo()
is run. rs.printSecondaryReplicationInfo()
时,成员可能会在主后面显示负时间值。This is expected if 如果rs.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.rs.printSecondaryReplicationInfo()
是在secondary复制一段不活动时间后的写入之后运行的,但在secondary从primary接收到具有最新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.secondary设备报告的滞后可能不能代表群集运行状况。负值并不表示secondary领先于primary。
To obtain the most current status for your replica set, run 要获取复制副本集的最新状态,请在主服务器上运行rs.printSecondaryReplicationInfo()
on the primary.rs.printSecondaryReplicationInfo()
。