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

Coordinator jobs with cron frequency should be invalidated upon submission if nothing would be materialized during run time

    XMLWordPrintableJSON

    Details

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

      Description

      If a user specifies a cron frequency that materializes nothing between start and end time, the coordinator job will remain "RUNNING" forever. This is due to the way we update coord jobs in StatusTransitService when we select coordinator jobs to be updated by last modified time of coordinator actions in function coordTransit(). A coordinator job with no materialized actions will never be selected to update the terminal status. This is not an issue before cron frequency is introduced since every coordinator job is guaranteed to have materialized actions.

        Attachments

        1. oozie-1578.patch
          8 kB
          Bowen Zhang

          Activity

            People

            • Assignee:
              bowenzhangusa Bowen Zhang
              Reporter:
              bowenzhangusa Bowen Zhang
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: