[
https://issues.apache.org/jira/browse/OOZIE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733929#comment-13733929
]
Alejandro Abdelnur commented on OOZIE-1443:
-------------------------------------------
+1
> forkjoin validation should not allow a fork to go to the same node multiple
> times
> ---------------------------------------------------------------------------------
>
> Key: OOZIE-1443
> URL: https://issues.apache.org/jira/browse/OOZIE-1443
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.2
> Reporter: Duc Anh Le
> Assignee: Robert Kanter
> Priority: Minor
> Fix For: trunk
>
> Attachments: dangling-node.png, OOZIE-1443.patch, OOZIE-1443.patch,
> workflow.xml
>
>
> The forkjoin validation code should not allow a fork to go to the same node
> multiple times. For example, this should not be allowed:
> Start -> ForkNode
> ForkNode -> (MR-1, MR-2, MR-2)
> MR-1 -> JoinNode
> MR-2 -> JoinNode
> JoinNode -> End
> We don't normally allow the same node to be executed multiple times because
> it will have one entry in the DB and the state will get overwritten and cause
> problems. In this case, the workflow gets stuck RUNNING.
> This should be a fairly trivial update to the forkjoin validation 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
