Re: Error message: 'Tried to update clock beyond the max. error.'

Thanks Todd. Much appreciated. Franco - Original Message - From: "Todd Lipcon" <t...@cloudera.com> To: user@kudu.apache.org Sent: Wednesday, November 1, 2017 9:46:15 PM Subject: Re: Error message: 'Tried to update clock beyond the max. error.' Thanks Franc

Re: Error message: 'Tried to update clock beyond the max. error.'

du.apache.org Sent: Wednesday, November 1, 2017 8:00:09 PM Subject: Re: Error message: 'Tried to update clock beyond the max. error.' What's the full log line where you're seeing this crash? Is it coming from tablet_bootstrap.cc, raft_consensus.cc, or elsewhere? -Todd 2017-11-01 15:45 GMT-0

Re: Error message: 'Tried to update clock beyond the max. error.'

Actually I think I understand the root cause of this. I think at some point NTP can switch the clock from a microseconds-based mode to a nanoseconds-based mode, at which point Kudu starts interpreting the results of the ntp_gettime system call incorrectly, resulting in incorrect error estimates

Re: Error message: 'Tried to update clock beyond the max. error.'

What's the full log line where you're seeing this crash? Is it coming from tablet_bootstrap.cc, raft_consensus.cc, or elsewhere? -Todd 2017-11-01 15:45 GMT-07:00 Franco Venturi : > Our version is kudu 1.5.0-cdh5.13.0. > > Franco > > > > > -- Todd Lipcon Software

Re: Error message: 'Tried to update clock beyond the max. error.'

Our version is kudu 1.5.0-cdh5.13.0. Franco

Re: Error message: 'Tried to update clock beyond the max. error.'

of those Kudu processes were down again, this > time with this new time sync related error message: > > > Tried to update clock beyond the max. error. > > > To try to address this new error, I brought down all the Kudu processes, > stopped ntpd, resync'd the time on all

Error message: 'Tried to update clock beyond the max. error.'

minutes later I restarted all the Kudu processes (one master and three tablet servers). A few minutes later a couple of those Kudu processes were down again, this time with this new time sync related error message: Tried to update clock beyond the max. error. To try to address this new