[
https://issues.apache.org/jira/browse/KUDU-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029145#comment-17029145
]
Alexey Serbin commented on KUDU-2573:
-------------------------------------
If using {{chronyd}} for time synchronization at Kudu nodes, the {{rtcsync}}
option
must be enabled in {{chrony.conf}}. Without {{rtcsync}}, the local machine's
clock
will always be reported as unsynchronized and Kudu masters and tablet servers
will not be able to start.
This
[excerpt|https://github.com/mlichvar/chrony/blob/994409a03697b8df68115342dc8d1e7ceeeb40bd/sys_timex.c#L162-L166]
from the chronyd's code explains the observed behavior.
> Fully support Chrony in place of NTP
> ------------------------------------
>
> Key: KUDU-2573
> URL: https://issues.apache.org/jira/browse/KUDU-2573
> Project: Kudu
> Issue Type: New Feature
> Components: clock, master, tserver
> Reporter: Grant Henke
> Assignee: Alexey Serbin
> Priority: Major
> Labels: clock
>
> This is to track fully supporting Chrony in place of NTP. Given Chrony is the
> default in RHEL7+, running Kudu with Chrony is likely to be more common.
> The work should entail:
> * identifying and fixing or documenting any differences or gaps
> * removing the experimental warnings from the documentation
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
