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 2020/02/03 20:09:07 UTC

[jira] [Updated] (KUDU-2940) built-in NTP client: measure and apply local clock skew

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

Alexey Serbin updated KUDU-2940:
--------------------------------
    Component/s: ntp-client

> built-in NTP client: measure and apply local clock skew
> -------------------------------------------------------
>
>                 Key: KUDU-2940
>                 URL: https://issues.apache.org/jira/browse/KUDU-2940
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: ntp-client
>            Reporter: Alexey Serbin
>            Priority: Minor
>
> In the initial implementation of the built-in NTP client, the skew of the local clock is not measured, but a highest possible skew threshold is used instead.  That makes the estimated error more conservative (assuming the local clock isn't went completely broken), but it would be nice to track and measure and use the actual skew of the local clock eventually.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)