[
https://issues.apache.org/jira/browse/KUDU-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048012#comment-17048012
]
Alexey Serbin commented on KUDU-2573:
-------------------------------------
After running several Kudu clusters at machines whose local clock is
synchronized with {{chronyd}}, I think we can declare that it's safe to use
{{chrony}} version 3.4 and newer instead of {{ntp}} on Kudu nodes.
The important configuration option to be turned on is {{rtcsync}} as described
[here|https://issues.apache.org/jira/browse/KUDU-2573?focusedCommentId=17029145&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17029145].
I updated the NTP troubleshooting docs: https://gerrit.cloudera.org/#/c/15320/
It's necessary to update the rest of the docs (e.g., building Kudu, etc.) and
before updating the resolution of this JIRA item.
> 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)
