Thanks Franco. I filed https://issues.apache.org/jira/browse/KUDU-2209 and put up a patch.
I'm also going to work on a change to try to allow Kudu to ride over brief interruptions in ntp synchronization status. Hopefully this will help folks who have some issues with occasional ntp instability. -Todd On Wed, Nov 1, 2017 at 6:31 PM, Franco Venturi <fvent...@comcast.net> wrote: > > From 'tablet_bootsratp.cc': > > 1030 14:29:37.324306 60682 tablet_bootstrap.cc:884] Check failed: > _s.ok() Bad status: Invalid argument: Tried to update clock beyond the max. > error. > > Franco > > > ------------------------------ > *From: *"Todd Lipcon" <t...@cloudera.com> > *To: *user@kudu.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-07:00 Franco Venturi <fvent...@comcast.net>: > >> Our version is kudu 1.5.0-cdh5.13.0. >> >> Franco >> >> >> >> >> > > > -- > Todd Lipcon > Software Engineer, Cloudera > > -- Todd Lipcon Software Engineer, Cloudera
