You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2019/09/14 05:49:00 UTC

[jira] [Updated] (KUDU-2936) built-in NTP client: simplified implementation to work with well behaved/trusted servers

     [ https://issues.apache.org/jira/browse/KUDU-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin updated KUDU-2936:
--------------------------------
    Summary: built-in NTP client: simplified implementation to work with well behaved/trusted servers  (was: Implement simplified built-in NTP client to work with well behaved servers)

> built-in NTP client: simplified implementation to work with well behaved/trusted servers
> ----------------------------------------------------------------------------------------
>
>                 Key: KUDU-2936
>                 URL: https://issues.apache.org/jira/browse/KUDU-2936
>             Project: Kudu
>          Issue Type: Sub-task
>            Reporter: Alexey Serbin
>            Assignee: Alexey Serbin
>            Priority: Major
>              Labels: clock, ntp
>
> 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. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)