38 ms·
Virtualization and time sync have had notorious problems. One ugly work around was frequent NTP polling and adjustments. NTP has a min and max poll interval, an
by spydum 10y ago
Virtualization and time sync have had notorious problems. One ugly work around was frequent NTP polling and adjustments. NTP has a min and max poll interval, and it determines how frequently it should poll automatically based on how far it sees drift happening. If it drifts pretty fast, it will quickly gravitate to the minpoll value, which is exactly what they show in their first graph: tons of polling at the minfrequency for certain hypervisors.
- raverbashing 10y agoI wonder, should this be solved with local NTP servers that resolve from the name pool.ntp.org?
- rhizome 10y agoI've found it to be good practice to run a single/few stratum 2 node(s) to serve local resources. To whatever degree, it's usually more important that these resources be more in sync with each other than with a satellite, which is fostered by having as few nodes as possible trying their luck over the internet to bogged down public stratum 1 NTP sources, instead configuring them to use a single source of time from a box more in its vicinity.
- snuxoll 10y agoMost corporate environments have long defaulted to having a strata 2 NTP server, as long as they use Windows since Kerberos requires clocks to be roughly in sync. With the advent of the cloud I see a lot of businesses forgoing any central IdM solution like AD or IPA and as a result don't tend to have an NTP server unless they explicitly configured one. All of my servers are joined to an AD or IPA domain, so they all use my local NTP servers by default.
- rincebrain 10y agoI knew that was once an issue, I'm surprised to find it's still an issue these days. In addition, even with minpoll, that's still a hell of a lot of clients abruptly polling him abusively.