> Op 1 april 2017 om 11:17 schreef mj <li...@merit.unu.edu>: > > > 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: >
That warning is there for a reason. I suggest you double-check your NTP and clocks on the machines. This should never happen in production. Are you running the MONs inside Virtual Machines? They are more likely to have drifting clocks. You could try the chrony NTP daemon instead of ntpd and make sure all MONs are peers from each other. Wido > > 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@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
