Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
The first implementation should be able to work with well-behaved NTP servers, not to be super strict to follow all RFC5905 provisions. It must accept list of NTP servers to work with, and by default it should be a list of publicly available NTP servers.
The client must not latch on non-synchronized NTP servers or set of servers whose true time is too far from each other.
tlipcon has posted a WIP for such an implementation already: see the 'Code Review' link.
Attachments
Issue Links
- requires
-
KUDU-2928 built-in NTP client: tests to evaluate the behavior of the client
- Resolved