Great, thank you Todd!
I assume nobody has any concerns with keeping the time source {{system}} by
default in Kudu 1.12 :) Otherwise, please let me know.
Kind regards,
Alexey
On Wed, Mar 18, 2020 at 10:10 AM Todd Lipcon
wrote:
> Sounds fine to me.
>
> -Todd
>
> On Wed, Mar 18, 2020 at 1:18
Sounds fine to me.
-Todd
On Wed, Mar 18, 2020 at 1:18 AM Alexey Serbin
wrote:
> Thank you all for the feedback!
>
> As Grant mentioned, parsing the configuration files of local NTP servers or
> getting the list of their peers via appropriate CLI was considered at some
> point in the scope of th
Thank you all for the feedback!
As Grant mentioned, parsing the configuration files of local NTP servers or
getting the list of their peers via appropriate CLI was considered at some
point in the scope of the 'auto' time source. However, this option didn't
look robust enough and no progress was m
I seem to recall discussing at one point the idea of setting multiple time
sources with a fallback behavior between them. In other words, the default
could be the built-in client, but in the case that the built-in client
can't contact NTP servers, we would fall back to the system NTP. This
switchin
I share the two concerns you highlighted, Alexey.
1. This would be a backwards incompatible change.
2. The default NTP server list could be unreachable, or could be a
poorer choice than whatever the cluster is currently using. Grant's
suggestion could mitigate that somewhat, but it's sort of weird
>
> Also, in
> case of Kudu clusters running without access to the internet, it will be
> necessary to point the built-in NTP client to some internal NTP servers
> since pool.ntp.org servers (the default servers for the built-in NTP
> client) might not be accessible.
>
I think this was discussed a
Hi,
I'd like to get feedback on the subj, please.
The built-in NTP client for Kudu masters and tablet servers was introduced
in Kudu 1.11.0. Back then, there were thoughts of switching to the
built-in client by default starting Kudu 1.12.
Since it's time for cutting 1.12 release branch pretty s
Hi,
I'd like to get feedback on the subj.
The built-in NTP client for Kudu masters and tablet servers was introduced
in Kudu 1.11.0. Back then, there were thoughts of switching to the
built-in client by default starting Kudu 1.12.
Since it's time for cutting 1.12 release branch pretty soon, I t
