You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2016/06/10 14:24:21 UTC
[jira] [Commented] (KUDU-1482) Kudu Tablet server crashes with -
Couldn't get the current time: Clock unsynchronized.
[ https://issues.apache.org/jira/browse/KUDU-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324514#comment-15324514 ]
Jean-Daniel Cryans commented on KUDU-1482:
------------------------------------------
Hi Shravan,
Per the error, the "maximum error" is too high. See http://getkudu.io/docs/troubleshooting.html#ntp
> 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)