Den ons 8 dec. 2021 kl 02:35 skrev mhnx <morphinwithyou@xxxxxxxxx>: > I've been building Ceph clusters since 2014 and the most annoying and > worst failure is the NTP server faults and having different times on > Ceph nodes. > > I've fixed few clusters because of the ntp failure. > - Sometimes NTP servers can be unavailable, > - Sometimes NTP servers can go crazy. > - Sometimes NTP servers can respond but systemd-timesyncd can not sync > the time without manual help. > > I don't want to deal with another ntp problem and because of that I've > decided to build internal ntp servers for the cluster. > > I'm thinking of creating 3 NTP servers on the 3 monitor nodes to get > an internal ntp server cluster. > I will use the internal NTP cluster for the OSD nodes and other services. > With this way, I believe that I'll always have a stable and fast time server. We do something like this. mons gather "calendar time" from outside ntp servers, but also peer against eachother, so if/when they drift away the mons drift away equal amounts, then all OSDs/RGWs and ceph clients pull time from the mons who serve internal ntp based on their idea of what time it is. Not using systemd, but both chronyd and ntpd allow you to set peers for which you sync "sideways" just to keep the pace in-between hosts. -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |