[
https://issues.apache.org/jira/browse/KUDU-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136331#comment-16136331
]
Todd Lipcon commented on KUDU-2097:
-----------------------------------
Ah.. well, that's evil -- it seems timesyncd just sets the max error to 0
rather than calculating it. So, kudu would "work" but its consistent scan modes
would be silently inconsistent due to inability to bound clock errors.
> Add note about disabling timesyncd
> ----------------------------------
>
> Key: KUDU-2097
> URL: https://issues.apache.org/jira/browse/KUDU-2097
> Project: Kudu
> Issue Type: Improvement
> Environment: Ubuntu with both timesyncd and ntp running after a fresh
> kudu install
> Reporter: Jens Kristian Geyti
> Priority: Trivial
>
> As kudu requires and automatically installs ntpd, it would be helpful to have
> the ntp troubleshooting document note that the user may to disable timesynd,
> as they'll likely conflict if running at the same time.
> Symptom:
> On ubuntu for example, that would cause `timedatectl status` to return
> ```
> NTP synchronized: no
> ```
> despite `ntpstat` returning
> ```
> ...
> synchronised to NTP server
> ...
> ```
> Disabling timesyncd (`systemctl disable systemd-timesyncd`) solves the
> conflict.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
