Hi,
Despite ntp, we keep getting clock skews that auto disappear again after
a few minutes.
To prevent the unneccerasy HEALTH_WARNs, I have increased the
mon_clock_drift_allowed to 0.2, as can be seen below:
root@ceph1:~# ceph --admin-daemon /var/run/ceph/ceph-osd.0.asok config show | grep clock
"mon_clock_drift_allowed": "0.2",
"mon_clock_drift_warn_backoff": "5",
"clock_offset": "0",
root@ceph1:~#
Despite this setting, I keep receiving HEALTH_WARNs like below:
ceph cluster node ceph1 health status became HEALTH_WARN clock skew detected on mon.1; Monitor clock skew detected mon.1 addr 10.10.89.2:6789/0 clock skew 0.113709s > max 0.1s (latency 0.000523111s)
Can anyone explain why the running config shows
"mon_clock_drift_allowed": "0.2" and the HEALTH_WARN says "max 0.1s
(latency 0.000523111s)"?
How come there's a difference between the two?
MJ
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
