[
https://issues.apache.org/jira/browse/OOZIE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13821783#comment-13821783
]
Alejandro Abdelnur commented on OOZIE-1550:
-------------------------------------------
Looks good, +1 after the following comments are addressed and jenkins passes
again:
* The method {{injectSubworkflowDepth}} should be
{{verifyAndInjectSubworkflowDepth}}
* The default of depth 10 seems too conservative and it may break complex
apps, I'd put something like 50
> 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)
