[OOZIE-2494] Cron syntax not handling DST properly

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 4.2.0, 5.0.0
• Fix Version/s: 5.1.0
• Component/s: coordinator
• Assignee: Kinga Marton
• Reporter: Dennis Pallett
• Created: 30/Mar/16 07:22
• Updated: 18/Jan/19 09:03
• Resolved: 03/May/18 14:33

Description

When specifying a coordinator frequency, you can also specify a "timezone". While the frequency is always calculated in UTC, the timezone’s DST rules are still applied. We can see this in the following two Coordinators, which ran across the DST shift (March 13 2016 at 2am) for the America/Los_Angeles timezone. The "el-UTC" job has "UTC" as the timezone, while the "el-LA" job has “America/Los_Angeles” as the timezone. Both jobs have a frequency of ${coord:days(1)}.

Job Name    : el-UTC
Start Time  : 2016-03-13 01:10 GMT | 2016-03-12 17:10 PST
---------------------------------------------------------
ID     Nominal Time (UTC)       Nominal Time (LA)
@1     2016-03-13 01:10 GMT     2016-03-12 17:10 PST
@2     2016-03-14 01:10 GMT     2016-03-13 18:10 PDT

Job Name    : el-LA
Start Time  : 2016-03-13 01:10 GMT | 2016-03-12 17:10 PST
---------------------------------------------------------
ID     Nominal Time (UTC)       Nominal Time (LA)
@1     2016-03-13 01:10 GMT     2016-03-12 17:10 PST
@2     2016-03-14 00:10 GMT     2016-03-13 17:10 PDT

As you can see, @2’s nominal time is adjusted to an hour earlier in the "el-LA" job, but not in the "el-UTC" job.

However, when running a similar set of jobs, but using cron syntax (10 1 1/1 * *, which indicates 1:10 every day of every month), this isn’t the case:

Job Name    : cron-UTC
Start Time  : 2016-03-13 01:08 GMT | 2016-03-12 17:08 PST
---------------------------------------------------------
ID     Nominal Time (UTC)       Nominal Time (LA)
@1     2016-03-13 01:10 GMT     2016-03-12 17:10 PST
@2     2016-03-14 01:10 GMT     2016-03-13 18:10 PDT

Job Name    : cron-LA
Start Time  : 2016-03-13 01:08 GMT | 2016-03-12 17:08 PST
---------------------------------------------------------
ID     Nominal Time (UTC)       Nominal Time (LA)
@1     2016-03-13 01:10 GMT     2016-03-12 17:10 PST
@2     2016-03-14 01:10 GMT     2016-03-13 18:10 PDT

As you can see, @2’s nominal time are the same in both the "cron-UTC" and "cron-LA" jobs. The "cron-LA" job should have the same nominal time as the "el-LA" job from earlier.

Issue Links

• is related to: OOZIE-2726 Flaky test due to daylight saving changes
• relates to: OOZIE-3214 Allow configurable timezone for coordinators
• links to: Review Board