[jira] [Updated] (OOZIE-1550) Create a safeguard to kill errant recursive workflows before they bring down oozie

["Robert Kanter (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Kanter updated OOZIE-1550:
---------------------------------

    Attachment: OOZIE-1550.patch

I created a patch that implements option 2 because (a) its more flexible and (b) it will catch infinite loops involving more than one workflow definition.  

By default, I set it to allow 10 subworkflows to be created; the 11th will cause the subwf action to do the error transition instead of starting the workflow.  The code is actually quite simple and just puts a depth counter in each subworkflow.

> Create a safeguard to kill errant recursive workflows before they bring down oozie
> ----------------------------------------------------------------------------------
>
>                 Key: OOZIE-1550
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1550
>             Project: Oozie
>          Issue Type: Improvement
>          Components: workflow
>    Affects Versions: 3.3.2, 4.0.0
>            Reporter: Robert Justice
>            Assignee: Robert Kanter
>              Labels: features
>         Attachments: OOZIE-1550.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)