You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2020/02/07 19:22:00 UTC
[jira] [Updated] (KUDU-3053) Make 'kudu cluster ksck' check and
report on the time source settings in a Kudu cluster
[ https://issues.apache.org/jira/browse/KUDU-3053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated KUDU-3053:
--------------------------------
Labels: clock (was: )
> 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
> Reporter: Alexey Serbin
> Priority: Major
> Labels: clock
>
> 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)