[OOZIE-3561] Forkjoin validation is slow when there are many actions in chain

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.1.0
• Fix Version/s: 5.3.0
• Component/s: core
• Labels: performance
• Assignee: Dénes Bodó
• Reporter: Dénes Bodó
• Created: 21/Nov/19 13:38
• Updated: 27/Nov/19 11:34
• Resolved: 27/Nov/19 11:34

Description

In case we have a workflow which has, let's say, 80 actions after each other:
a1 -> a2 -> ... a80
then the validator code "never" finishes.

Currently the validation (in my understanding) does depth first checks from the start node and runs in time of n! . This is confirmed as when we split this huge workflow into two 40-element workflow then we get 2x ~40!-step in validation instead of ~80! steps.

Guys, could you please confirm or disprove my theory?

Thanks

Issue Links

• is caused by: OOZIE-1978 Forkjoin validation code is ridiculously slow in some cases