Hi all,
Did anyone else experience some bizarre issues with oozie's coordinator after
daylight savings time change? Our coordinator was submitted weeks ago at 7pm
and scheduled to run every 24 hours. The coordinator is supposed to wait for
an input dataset though, so it normally waits until about midnight before the
workflow is materialized. However, ever since daylight savings on 11/1, the
coordinator would no longer wait and just materialize a workflow instance
immediately at 7pm.
Here's a part of our coordinator definition:
<coordinator-app xmlns="uri:oozie:coordinator:0.2" name="merge"
start="${coord:conf('schedule.start')}"
end="${coord:conf('schedule.end')}"
timezone="US/Pacific"
frequency="${coord:hours(24)}">
<controls>
<timeout>-1</timeout>
<concurrency>1</concurrency>
</controls>
<datasets>
<dataset name="all-iters-complete" frequency="${coord:days(1)}"
initial-instance="${coord:conf('start')}"
timezone="US/Pacific">
<uri-template>${coord:conf('namenode')}/process_info/${YEAR}_${MONTH}_${DAY}</uri-template>
<done-flag>up_to_eod_iters_SUCCESS</done-flag>
</dataset>
</datasets>
<input-events>
<data-in name="input" dataset="all-iters-complete">
<instance>${coord:current(0)}</instance>
</data-in>
</input-events>
...
The dataset /process_info/2015_11_01/up_to_eod_iters_SUCCESS gets created early
on 2015_11_02, but the workflow kicked off before then.
One configuration we had that might affect this was in our oozie-site.xml:
<property>
<name>oozie.processing.timezone</name>
<value>GMT-0800</value>
</property>
Thanks!
Alvin
