Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

How to schedule an Oozie job to run at 8PM EDT?

avatar
Expert Contributor
 
1 ACCEPTED SOLUTION

avatar

Look at the Oozie coordinator documentation, the timezone value will be "America/New_York" and start would be something like "2015-10-12T08:00Z". Alternatively you can do a cron like thing, see the example in the following blog. Based on that it can be something like:

<coordinator-app name="weekdays-at-eight-pm"
  frequency="0 20 * * 2-6"
  start="${start}" end="${end}" timezone="America/New_York"
  xmlns="uri:oozie:coordinator:0.2">
...
</coordinator-app>

View solution in original post

4 REPLIES 4

avatar

Look at the Oozie coordinator documentation, the timezone value will be "America/New_York" and start would be something like "2015-10-12T08:00Z". Alternatively you can do a cron like thing, see the example in the following blog. Based on that it can be something like:

<coordinator-app name="weekdays-at-eight-pm"
  frequency="0 20 * * 2-6"
  start="${start}" end="${end}" timezone="America/New_York"
  xmlns="uri:oozie:coordinator:0.2">
...
</coordinator-app>

avatar
New Contributor

Will this be a problem when DayLightSaving change takes place from EDT TO EST.

Also I tried your solution, and the coordinator actions are being generated at 8 PM UTC timezone not 8 PM EDT.

From what I read in other blogs, Do I need to change my oozie.processing.timezone to EDT to make the above thing work?

avatar
New Contributor

This is not working gives paramter frequency must be an integer Parsing error for input string "0 20 * * 2-6"

avatar
New Contributor

I had the same issue, because I put the frequency in the dataset as a cron, we can't actually do that.

Here is my example :

<coordinator-app name="weekdays-at-two-am"
frequency="0 2 * * 2-6"
start="${start} "
end="${end}"
timezone="Europe/Paris"
xmlns="uri:oozie:coordinator:0.4">
<datasets>
	<dataset name="my_dataset_name"
	 	frequency="${coord:days(1)}"
	 	initial-instance="2017-12-28T02:00+0100"
	 	timezone="Europe/Paris">
		<uri-template>${my_path}/${YEAR}${MONTH}${DAY}</uri-template>
		<done-flag>my_flag</done-flag>
	</dataset>
</datasets>
<input-events>
    <data-in name="log_input_name" dataset="my_dataset_name">
        <instance>${coord:current(0)}</instance>
    </data-in>
</input-events>

my coordinator is lunched with the cron at first (line 2), but it verifies the second condition which looking every day (line9) for the flag of the current day (line 18)