[
https://issues.apache.org/jira/browse/OOZIE-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andras Piros updated OOZIE-3173:
--------------------------------
Attachment: OOZIE-3173.002.patch
> Coordinator job with frequency using cron syntax creates only one action in
> catchup mode
> ----------------------------------------------------------------------------------------
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
> Issue Type: Bug
> Components: coordinator
> Affects Versions: 5.0.0b1
> Reporter: Andras Piros
> Assignee: Andras Piros
> Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time
> lies also in the past), would create only one action, independent of
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now,
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in
> the past, and {{throttle}} is {{15}} -> ten actions should be created
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
