Re: tserver died by clock unsync.

Hi Alexey, Thank you for your kind answer! Best, Jason 2017-06-17 4:53 GMT+09:00 Alexey Serbin : > Hi Jason, > > I think the workaround you mentioned (i.e. replacing LOG(FATAL) with > LOG(WARNING) in the cited code snippet) is not safe at all. If > ntp_gettime() returns TIME_ERROR code, that

Re: tserver died by clock unsync.

Hi Jason, I think the workaround you mentioned (i.e. replacing LOG(FATAL) with LOG(WARNING) in the cited code snippet) is not safe at all. If ntp_gettime() returns TIME_ERROR code, that means the 'now_usec' variable might be left uninitialized, and the code relying on the HybridClock::NowWit

Re: tserver died by clock unsync.

Hi. Congrat. Apache Kudu 1.4.0 To prevent tserver from dying accidentally, I've changed LOG(FATAL) to LOG(WARNING) I wanted to know it is safe to continue if ntp_gettime() in GetClockTime

tserver died by clock unsync.

Hi, I'm using Apache Kudu 1.4.0 Yesterday, 6 tservers die at the same time. Following message is logged for each tserver. F0614 14:58:32.868551 111454 hybrid_clock.cc:227] Couldn't get the current time: Clock unsynchronized. Status: Service unavailable: Error reading clock. Clock considered