[
https://issues.apache.org/jira/browse/OOZIE-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531284#comment-14531284
]
Jaydeep Vishwakarma commented on OOZIE-1837:
--------------------------------------------
Yes, The launch time setting happens through
{{LauncherMapperHelper.setupYarnRestartHandling}} from oozie server side. It
is being used by {{LauncherMainHadoopUtils}} which runs on one of the node.
> LauncherMainHadoopUtils sensitive to clock skew
> -----------------------------------------------
>
> Key: OOZIE-1837
> URL: https://issues.apache.org/jira/browse/OOZIE-1837
> Project: Oozie
> Issue Type: Bug
> Environment: Oozie 4.0.0 (CDH5)
> Reporter: Lars Francke
> Priority: Minor
>
> The method {{getChildYarnJobs}} in {{LauncherMainHadoopUtils}} can fail with
> a message like {{begin > end in range (begin, end): (1399972474014,
> 1399972473948)}}.
> {code}
> startTime = Long.parseLong((System.getProperty("oozie.job.launch.time")));
> ....
> gar.setStartRange(startTime, System.currentTimeMillis());
> {code}
> I guess this is happening when the server on which the launch time was set
> has a different time then the one this task is running on. In our case there
> was a skew of about 8 seconds which caused all of our jobs that hit this
> server to fail.
> I understand that skew in clocks is generally not a good idea but I feel that
> Oozie could be a bit more resilient here or print a better warning maybe?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
