kudu service are getting down frequently

[#1]

Hi, Kudu crashing frequently with error Couldn't get the current time: Clock unsynchronized. Status: Service unavailable: Error reading clock. Clock considered unsynchronized however i am not seeing any clock offset error in cluster . kudu documents says this could be because of network delay between NTP server and kudu host. but kudu is sharing host with database while datanode is not reporting clock offset error . what could be the reason .

[#2]

I would strongly recommend NOT running with hybrid time turned off for one
simple reason: tablet history GC will not work. Therefore when you delete
or update a row the history of that data will be kept forever. Eventually
you may run out of disk space. The one exception is if you drop a table,
then the data for that table will be permanently removed regardless of
hybrid time.

[#3]

You need to configure NTP correctly. "Four NTP servers is the recommended minimum. Four servers protects against one incorrect timesource, or "falseticker". " for tips in configuring NTP. https://access.redhat.com/solutions/58025

[#4]

We have NTP servers, wondering why only Kudu impacted.

NTP and clock offset impacted a complete node and not a service.