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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0b1
• Fix Version/s: 5.0.0
• Component/s: coordinator
• Assignee: Andras Piros
• Reporter: Andras Piros
• Created: 05/Feb/18 20:36
• Updated: 09/Apr/18 15:15
• Resolved: 09/Feb/18 17:03

Description

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

Issue Links

• links to: ReviewBoard link