[
https://issues.apache.org/jira/browse/KUDU-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325266#comment-15325266
]
Shravan Pabba commented on KUDU-1482:
-------------------------------------
Will bump up the max_clock_sync_error_usec to 20 seconds. Guess my home network
is flaky
> Kudu Tablet server crashes with - Couldn't get the current time: Clock
> unsynchronized.
> --------------------------------------------------------------------------------------
>
> Key: KUDU-1482
> URL: https://issues.apache.org/jira/browse/KUDU-1482
> Project: Kudu
> Issue Type: Bug
> Components: tserver
> Affects Versions: 0.8.0
> Reporter: Shravan Pabba
> Priority: Critical
>
> Tablet server crashed with,
> Jun 8, 8:28:51.868 PM FATAL hybrid_clock.cc:228
> Couldn't get the current time: Clock unsynchronized. Status: Service
> unavailable: Error: Clock synchronized but error wastoo high (10023223 us).
> Don't actually see any problems with clock synchronization on the server.
> Date seems to be in sync (ntpd running fine and no errors).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
