You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/02/05 20:37:00 UTC

[jira] [Created] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

Andras Piros created OOZIE-3173:
-----------------------------------

             Summary: 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


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:
* 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)