[OOZIE-1443] forkjoin validation should not allow a fork to go to the same node multiple times

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.3.2
• Fix Version/s: 4.1.0
• Assignee: Robert Kanter
• Reporter: Duc Anh Le
• Created: 03/Jul/13 14:54
• Updated: 09/Dec/14 00:45
• Resolved: 08/Aug/13 20:46

Description

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.

Issue Links

• is related to: OOZIE-1403 forkjoin validation blocks some valid cases involving decision nodes
• is related to: OOZIE-1035 Improve forkjoin validation to allow same errorTo transitions