Learn about the change in certain functionality of Kudu that has resulted in a change in
behavior from the previously released version to this version of Cloudera Runtime.
- Summary:
-
The logic to select a particular time source when the pseudo-source
'auto' used for --time_source is changed.
- Previous behavior:
-
The 'system' time source would be auto-selected if a Kudu server with
--time_source=auto is run in an environment where the instance detector is
not aware of a dedicated NTP server. Those are usually available through the host-only
interface, at least for EC2 and GCE instances.
- New behavior:
-
The 'builtin' time source would be auto-selected if a Kudu server runs with
--time_source=auto in an environment where the instance detector isn't aware
of dedicated NTP servers and the --builtin_ntp_servers flag is set to a valid
value. Otherwise, if --builtin_ntp_servers flag is set to an empty/invalid
value, 'system' becomes the auto-selected time source for platforms supporting
get_ntptime() API, otherwise the catch-all case is used to auto-select
'system_unsync' as the time source.
