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

Create a safeguard to kill errant recursive workflows before they bring down oozie

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.3.2, 4.0.0
    • Fix Version/s: 4.1.0
    • Component/s: workflow
    • Labels:

      Description

      If a user creates an errant workflow with a sub-workflow that calls the workflow again, without a proper decision node to exit the workflow, it will continue to create numerous jobs until the oozie server is saturated. A user recently had 400,000 running jobs and oozie was non-responsive. I would suggest we have some method of preventing a user from taking out oozie, such as a max running jobs
      parameter.

        Attachments

        1. OOZIE-1550.patch
          9 kB
          Robert Kanter
        2. OOZIE-1550.patch
          9 kB
          Robert Kanter

          Issue Links

            Activity

              People

              • Assignee:
                rkanter Robert Kanter
                Reporter:
                rjustice Robert Justice
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: