Alexey Serbin created KUDU-3047:
-----------------------------------
Summary: Implement automatic selection of the time source for Kudu
Key: KUDU-3047
URL: https://issues.apache.org/jira/browse/KUDU-3047
Project: Kudu
Issue Type: Improvement
Reporter: Alexey Serbin
With KUDU-2936 and KUDU-3009 implemented, it's now possible to automatically
select time source for Kudu masters and tablet servers. Assuming Kudu is not
going to be deployed in hybrid environments (like half of the cluster in GCE,
another in Azure), it looks like a reliable way to get the same time source
auto-selected across a Kudu cluster.
A few principles of the time source auto-selection are the following:
* in well recognized environments guaranteed to provide dedicated NTP service,
use the provided NTP server(s) for the built-in client, so it's not necessary
to require NTP server running at Kudu nodes
* in well recognized environments known not to provide NTP service, require the
clock to be synchronized by an external NTP daemon
* report on the selected time source when the diagnostic tooling is run,
showing warnings if the time source happen to set different for different
tablet servers in the cluster
use the {{built\-in}} client with information provided by DHCP (if any),
In detail:
* AWS: use {{built\-in}}; run the built-in NTP client auto-configuration, if
enabled
* GCE: use {{built\-in}}; run the built-in NTP client auto-configuration, if
enabled
* Azure: use {{system}}; optionally try to configure the built-in client using
the information on NTP servers provided via DHCP for the host
* not recognized as cloud environment: use {{system}}; optionally try to
configure the built-in client using the information on NTP servers provided via
DHCP for the host
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
