[OOZIE-1513] Workflow stays in running if Fork/join validation or loop detection fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: trunk
• Fix Version/s: 4.1.0
• Assignee: Mona Chitnis
• Reporter: Mona Chitnis
• Created: 26/Aug/13 17:36
• Updated: 09/Dec/14 00:45
• Resolved: 04/Sep/13 21:00

Description

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.

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

Issue Links

• breaks: OOZIE-1530 Fork-join mismatch makes workflow Failed but some actions stay Running