Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3173

Coordinator job with frequency using cron syntax creates only one action in catchup mode

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.0b1
    • Fix Version/s: 5.0.0
    • Component/s: coordinator
    • Labels:
      None

      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

        Attachments

        1. OOZIE-3173.002.patch
          8 kB
          Andras Piros
        2. OOZIE-3173.001.patch
          7 kB
          Andras Piros

          Activity

            People

            • Assignee:
              andras.piros Andras Piros
              Reporter:
              andras.piros Andras Piros

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment