[
https://issues.apache.org/jira/browse/KUDU-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin resolved KUDU-3053.
---------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
This is implemented with
[a9afbce14454f9b03b9cc5a699a09f4f9935da58|https://github.com/apache/kudu/commit/a9afbce14454f9b03b9cc5a699a09f4f9935da58]
> Make 'kudu cluster ksck' check and report on the time source settings in a
> Kudu cluster
> ---------------------------------------------------------------------------------------
>
> Key: KUDU-3053
> URL: https://issues.apache.org/jira/browse/KUDU-3053
> Project: Kudu
> Issue Type: Improvement
> Components: CLI
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Labels: clock
> Fix For: 1.12.0
>
>
> Since the time source for the hybrid clock is now configurable (and even
> auto-configurable), it's important to ensure that the time source is
> configured consistently across the cluster. At least, there should be a way
> to spot discrepancies in the time source across all Kudu servers
> (masters/tservers).
> Let's add extra functionality into the {{kudu cluster ksck}} logic to verify
> that the time source is configured uniformly across Kudu cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
