You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/08/18 02:52:00 UTC

[jira] [Commented] (KUDU-2097) Add note about disabling timesyncd

    [ https://issues.apache.org/jira/browse/KUDU-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131649#comment-16131649 ] 

Todd Lipcon commented on KUDU-2097:
-----------------------------------

Do you think on systems with timesyncd available we should change the rpm/deb requirement to allow either ntpd or timesyncd? Any idea if kudu works with timesyncd? i.e does it properly update the maxerror estimate in the kernel?

> 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)