Hi Gaurav, IIRC, it should say why it's failing the ForkJoin validation. What does it say?
There are two reasons why we allow disabling ForkJoin validation: 1. In case there's a bug in the ForkJoin validation code (it's very complicated), there's a workaround to allow skipping it 2. In larger workflows, the ForkJoin validation code can take a very long time to finish (on the order of hours or days), so there needs to be a way to skip it. (OOZIE-1978 <https://issues.apache.org/jira/browse/OOZIE-1978> is open to improve this) As for whether or not it's safe to disable the validation, if the workflow is working fine, then it's okay. The main purpose of the ForkJoin validation is to fail incorrect workflows at submission time, rather than during runtime. I believe that there are some technically incorrect ForkJoin cases where Oozie can still work just fine, even though it's wrong. You've either done that or found a bug in the ForkJoin validation code :) Can you post the reason and the workflow so I can see what it's complaining about? - Robert On Wed, Feb 18, 2015 at 5:15 PM, Gaurav Aggarwal < [email protected]> wrote: > Hi, > > I have a workflow which fails ForkJoin validation in oozie but works fine > if I set oozie.wf.validate.ForkJoin=false. > > Is it safe to set oozie.wf.validate.ForkJoin=false ? > > I want to understand potential runtime issues that can be created if I > disable fork join validation. > > Thanks, > Gaurav >
