If its of any help, the error is sourced from the client's values. The client here is Hue, which is sending the jobtracker value for the WF as the MR1 URL instead of the MR2 RM one. As a result, since the Oozie server is pre-tuned to only talk to YARN service, it rejects the client (Hue) cause its passed JT location is invalid for the current whitelist of RMs. You should look further into why Hue is still sending the MR1 properties along, instead of MR2. Perhaps the values are embedded into the WF application, or perhaps the Hue service has not been configured to also talk to the YARN service (via its CM Hue Configuration page, just like how you switched Oozie to talk to YARN). The Oozie server isn't at fault here.
... View more
