-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Replication 2022-02-07
Having a replSetHeartbeat command's ReplSetHeartbeatResponse include the node's oplog head time would allow oplog windows to be calculated from replSetGetStatus and as a result recorded in FTDC.
For example:
MongoDB Enterprise replset:SECONDARY> db.adminCommand({ replSetHeartbeat: "replset", configVersion: 6, from: "192.168.2.100:27019", term: 3 }) { "ok" : 1, "state" : 2, "v" : 6, "configTerm" : 3, "set" : "replset", "syncingTo" : "192.168.2.13:27018", "term" : NumberLong(3), "primaryId" : NumberLong(1), "durableOpTime" : { "ts" : Timestamp(1642177853, 1), "t" : NumberLong(3) }, "durableWallTime" : ISODate("2022-01-14T16:30:53.341Z"), "opTime" : { "ts" : Timestamp(1642177853, 1), "t" : NumberLong(3) }, /** Something like this maybe **/ "oldestOpTime" : { "ts" : Timestamp(1642177853, 1), "t" : NumberLong(3) }, /**********************************/ "wallTime" : ISODate("2022-01-14T16:30:53.341Z"), "electable" : true, "$clusterTime" : { "clusterTime" : Timestamp(1642177853, 1), "signature" : { "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="), "keyId" : NumberLong(0) } }, "operationTime" : Timestamp(1642177853, 1) }
- duplicates
-
SERVER-62941 Update FTDCServerStatusCommandCollector to include oplog metrics from serverStatus command
- Closed