You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2013/09/04 02:29:52 UTC
[jira] [Commented] (OOZIE-1513) Workflow stays in running if
Fork/join validation or loop detection fails
[ https://issues.apache.org/jira/browse/OOZIE-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757300#comment-13757300 ]
Hadoop QA commented on OOZIE-1513:
----------------------------------
Testing JIRA OOZIE-1513
Cleaning local svn workspace
----------------------------
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-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:red}-1{color} the patch does not add/modify any testcase
{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:red}-1 COMPILE{color}
. {color:green}+1{color} HEAD compiles
. {color:green}+1{color} patch compiles
. {color:red}-1{color} the patch seems to introduce 1 new javac warning(s)
{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:green}+1 TESTS{color}
. Tests run: 1316
{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/751/
> Workflow stays in running if Fork/join validation or loop detection fails
> -------------------------------------------------------------------------
>
> Key: OOZIE-1513
> URL: https://issues.apache.org/jira/browse/OOZIE-1513
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
> Attachments: OOZIE-1513.patch
>
> Original Estimate: 6h
> Remaining Estimate: 6h
>
> If some jobs have configured their workflow definition wrongly with improper use of fork-join combination, in some occurrences the jobs did not go to FAILED. Recovery service keeps picking up and running them again and again, so log is full of errors.
> {code}
> 2012-10-03 19:40:54,035 ERROR SignalXCommand:536 - USER[joe] GROUP[users] TOKEN[-] APP[my-oozie-app] JOB[0001800-120927185459177-oozie-wrkf-W] ACTION[0001800-120927185459177-oozie-wrkf-W@streaming-job] XException,
> org.apache.oozie.command.CommandException: E0720: Fork/join mismatch, node [join]
> at org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:165)
> at org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:63)
> at org.apache.oozie.command.XCommand.call(XCommand.java:277)
> at org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.oozie.workflow.WorkflowException: E0720: Fork/join mismatch, node [join]
> at org.apache.oozie.workflow.lite.JoinNodeDef$JoinNodeHandler.loopDetection(JoinNodeDef.java:47)
> at org.apache.oozie.workflow.lite.LiteWorkflowInstance.signal(LiteWorkflowInstance.java:206)
> at org.apache.oozie.workflow.lite.LiteWorkflowInstance.signal(LiteWorkflowInstance.java:287)
> at org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:162)
> ... 6 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira