[
https://issues.apache.org/jira/browse/KUDU-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303902#comment-16303902
]
Todd Lipcon commented on KUDU-2242:
-----------------------------------
I think it's not a bad idea, so long as we don't cause a bad experience of a
very slow error response if NTP is just plain not running. Perhaps a reasonable
approach is to try to detect whether NTP is running at all, and if it is
running but not yet synchronized, wait a configurable number of seconds?
We could also consider shelling out to 'ntp-wait'. But then that also makes me
wonder: should this be included in whatever init scripts or service management
framework starts kudu rather than in Kudu itself?
> Wait for NTP synchronization on startup
> ---------------------------------------
>
> Key: KUDU-2242
> URL: https://issues.apache.org/jira/browse/KUDU-2242
> Project: Kudu
> Issue Type: Improvement
> Components: server
> Reporter: Jean-Daniel Cryans
> Priority: Critical
>
> A common issue when restarting servers is that the clock won't be
> synchronized right away and the Kudu services will refuse to start. We should
> be more tolerant to this, maybe a few simple retries?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
