Will Berkeley has posted comments on this change. ( http://gerrit.cloudera.org:8080/10548 )
Change subject: [WIP] KUDU-2242 Wait for NTP synchronization on startup ...................................................................... Patch Set 1: > I wonder if we should condition this on either the system uptime or > the uptime of the ntpd/chrony process? Does that mean you think there's too little realistic chance of Kudu starting up after the machine has been up for a while and NTP is temporarily unsynchronized? I've seen a cluster in the wild where NTP had brief problem periods, though in that case the clocks stayed synchronized but the error bounds got big (which crashed the cluster). > Also perhaps we can detect when it's not running at all, and not wait? That should already basically happen at least for ntp-wait since it will fail immediately if it can't connect to the ntp daemon. I have to test it for chrony. -- To view, visit http://gerrit.cloudera.org:8080/10548 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I6082c5d35ed0d230d91c61734e7b5a351e50933b Gerrit-Change-Number: 10548 Gerrit-PatchSet: 1 Gerrit-Owner: Will Berkeley <[email protected]> Gerrit-Reviewer: Kudu Jenkins Gerrit-Reviewer: Mike Percy <[email protected]> Gerrit-Reviewer: Todd Lipcon <[email protected]> Gerrit-Reviewer: Will Berkeley <[email protected]> Gerrit-Comment-Date: Wed, 30 May 2018 20:14:04 +0000 Gerrit-HasComments: No
