Hi Richard,
Why not parameterize the coordinator "start" time? This start time should
be when you wish the first instance to run.
E.g. <coordinator-app name="test-coord"
frequency="${coord:hours(1)}"
start=${my_start_time}
end="2013-11-04T24:00Z">
--
Mona
On 11/4/13 10:24 AM, "Ross, Richard (Truven Health)"
<[email protected]> wrote:
>Forgot the Oozie version info: Oozie 3.3.2.
>
>Thanks,
>Richard.
>
>-----Original Message-----
>From: Ross, Richard (Truven Health)
>[mailto:[email protected]]
>Sent: Monday, November 04, 2013 1:22 PM
>To: [email protected]
>Subject: Stopping Oozie Coordinator from running in the past
>
>Hello:
>
>I have been playing around with Oozie Coordinator and noticed that when a
>coordinator definition is submitted, if the start value is in the past,
>it will run the workflow based on this past start and frequency values to
>"catch up" to the current time. Is there a way to tell Oozie to not run
>any workflows from the past?
>
>For example, if the actual time when the Coordinator definition is
>submitted is 2013-11-04T12:30Z and the coordinator.xml is:
>
><coordinator-app name="test-coord"
> frequency="${coord:hours(1)}"
> start="2013-11-04T00:00Z"
> end="2013-11-04T24:00Z"
> timezone="UTC" xmlns="uri:oozie:coordinator:0.1">
>
> <action>
> <workflow>
> .
> .
> .
> </workflow>
> </action>
></coordinator-app>
>
>then workflow will run from 2013-11-04T00:00Z to 2013-11-04T12:00Z until
>it catches up (i.e., 12 or 13 times. Not sure as this is an example) to
>the current time. It will then follow the schedule. I would like it to
>just execute the next time the schedule is satisfied (i.e., is
>2013-11-04T13:00Z)
>
>Thanks,
>Richard.
