Closed jackjansen closed 6 months ago
Noticed this problem purely by chance, while running on the same machine as the orchestrator. The measurements are very imprecise, probably due to the way BestHTTP is structured.
I got this message:
stats: seq=2, ts=3227.079, component=OrchestratorController, orchestrator_ntptime_ms=1694040826972, localtime_behind_ms=-106, uncertainty_interval_ms=106
And, indeed, a machine is mathematically behind itself by 106 ms with an uncertainty of 106 ms, but still...
No longer relevant with orchestrator v2.
Noticed this problem purely by chance, while running on the same machine as the orchestrator. The measurements are very imprecise, probably due to the way BestHTTP is structured.
I got this message:
And, indeed, a machine is mathematically behind itself by 106 ms with an uncertainty of 106 ms, but still...