[
https://issues.apache.org/jira/browse/KUDU-2927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921547#comment-16921547
]
Alexey Serbin commented on KUDU-2927:
-------------------------------------
There are a couple of changelists which already landed in this context:
* https://github.com/apache/kudu/commit/0f38821c4867b86044be22dbceb80c7bc04b5d33
* https://github.com/apache/kudu/commit/efda91850e57a904f1b0e7858a3e2d8c4e2b7241
> A testbench to evaluate and test the behavior of the built-it NTP client
> ------------------------------------------------------------------------
>
> Key: KUDU-2927
> URL: https://issues.apache.org/jira/browse/KUDU-2927
> Project: Kudu
> Issue Type: Task
> Components: test
> Affects Versions: 1.11.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
>
> In the context of using the built-in NTP client in Kudu (see WIP patch from
> Todd: https://gerrit.cloudera.org/#/c/7477/), it's necessary to build a
> testbench to evaluate and test the behavior of the built-it NTP client.
> The essential part of the testbench is NTP server: it seems chrony is a good
> alternative since it supports server-only mode, so it's possible to run
> {{chronyd}} which servers as an NTP server for various test scenarios
> (without hustle of actually driving the system clock).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
