-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication, Replication - Oplog and Recovery
-
Repl 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Log and emit a metric if a member's last_xxx timestamp goes back in time through a heartbeat or replSetUpdatePosition directly from that node.
Each node keeps track of the last heartbeat response it had from another node. We use this info for sync source selection.
But we separately keep track of every node known lastWritten / lastApplied / lastDurable updated through heartbeat or the replSetUpdatePosition command, and this is not overrode if the new optime is not greater than the previously known optime. We only use this information for write concern and commit point updates.
Having a metric that would tell us if a node has gone back in time could help us investigate data loss issues in the future.
AI taken from WRITING-39616.