Actions
Feature #17597
openleader should recognize its own clock skew instead of assuming the whole cluster is skewed
Status:
New
Priority:
Normal
Assignee:
-
Category:
Monitor
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
In a cluster with 5 monitors where only one of the monitors had a crashed ntpd, the check for determining clock skew incorrectly reported that the other four mons had clock skew (where ntp was running fine). From the point of view of the monitor with the crashed ntpd this might be true, but now for a cluster as a whole. After restarting the failed ntpd the clock skew issue was resolved. It looks that the logic determining clock skew could be improved on this point. Better warning/error messages help to pinpoint/resolve the issue faster.
Actions