[
https://issues.apache.org/jira/browse/OOZIE-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823067#comment-13823067
]
Hadoop QA commented on OOZIE-1550:
----------------------------------
Testing JIRA OOZIE-1550
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
. {color:green}+1{color} the patch does not introduce any @author tags
. {color:green}+1{color} the patch does not introduce any tabs
. {color:green}+1{color} the patch does not introduce any trailing spaces
. {color:green}+1{color} the patch does not introduce any line longer than
132
. {color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
. {color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
. {color:green}+1{color} the patch does not seem to introduce new Javadoc
warnings
{color:green}+1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
. {color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
. {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
. Tests run: 1352
. Tests failed: 1
. Tests errors: 0
. The patch failed the following testcases:
. testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
{color:green}+1 DISTRO{color}
. {color:green}+1{color} distro tarball builds with the patch
----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/oozie-trunk-precommit-build/886/
> 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, 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)
