[
https://issues.apache.org/jira/browse/KUDU-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke updated KUDU-2935:
------------------------------
Labels: clock roadmap-candidate (was: clock)
> Implement built-in NTP client
> -----------------------------
>
> Key: KUDU-2935
> URL: https://issues.apache.org/jira/browse/KUDU-2935
> Project: Kudu
> Issue Type: New Feature
> Components: clock, master, tserver
> Affects Versions: 1.11.0
> Reporter: Alexey Serbin
> Priority: Major
> Labels: clock, roadmap-candidate
>
> It would be nice to add a stripped-down implementation of built-in NTP client
> without any reliance on the kernel NTP discipline. The built-in client
> should maintain wall clock synchronized with NTP servers, and calling
> {{WalltimeWithError()}} should return wall clock timestamp with the
> estimation of error/offset from true time. Having built-in NTP client would
> provide more control over acceptable clock error and jitter acceptable for
> HybridTime timestamp generation.
> From the operability perspective, it would make it easier to run Kudu in
> containerized environments and overall make it easier for users to configure
> NTP even if they don't have superuser privileges at a node.
> The very first implementation should be good enough to work with properly
> configured and well behaving NTP servers, not necessarily being full-featured
> and 100% RFC-compliant NTP client. Later on, we can add more features and
> constraints to protect against misbehaving and rogue NTP servers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
