[SERVER-26588] Sync token for mongod logs Created: 11/Oct/16  Updated: 06/Dec/22  Resolved: 27/May/22

Status: Closed
Project: Core Server
Component/s: Diagnostics, Replication
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: Improvement Priority: Major - P3
Reporter: Daniel Coupal Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Participants:

 Description   

If would be helpful if we could rely on a piece of information from the mongod logs to synchronize the information in a common timeline.
Sometimes the logs have:

  • no timezone information
  • clock drift between hosts

which makes it difficult.

One possibility would be to use a unique token or an information from a heartbeat and have the 2 hosts log this info in there corresponding logs. Searching for the string, in both logs, would give you a synchronization point.
For example:

  • host A records a time and a unique ID
  • host A sends the info to host B (may already be available through the heartbeat)
  • host A logs the info (the recorded time would be different than the log time, however we care about the first one)
  • host B logs the info received, with its own timestamp
  • host A or B would add the perceived latency it knows about the other host.

This token should only be needed once per couple of hosts at a frequency of once per hour, or once per day, or once per log file.


Generated at Thu Feb 08 04:12:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.