[OOZIE-1837] LauncherMainHadoopUtils sensitive to clock skew

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.3.0

Environment

Oozie 4.0.0 (CDH5)

• Assignee: Robert Kanter
• Reporter: Lars Francke
• Created: 13/May/14 09:44
• Updated: 02/Dec/16 21:01
• Resolved: 16/Jul/15 22:01

Description

The method getChildYarnJobs in LauncherMainHadoopUtils can fail with a message like begin > end in range (begin, end): (1399972474014, 1399972473948).

startTime = Long.parseLong((System.getProperty("oozie.job.launch.time")));
....
gar.setStartRange(startTime, System.currentTimeMillis());

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?