When I run an oozie hive action with "SET hive.execution.engine=mr;" I see in Resource Manager UI 2 applications :
One application that corresponds to my action HIVE (insert into hdfs...) with the name i fixed and application Type = Map reduce and another application with the name like "HIVE-dhhdgdgjdg....) and a type of engine is TEZ !!!
I note that the default engine on my cluster HDP is TEZ and I just change on Map reduce in my Oozie Action:
SET hive.execution.engine=mr; INSERT OVERWRITE TABLE hdfs.tab1 SELECT a,b,c FROM cassandra.tab1;
Have you any idea about the source of the second TEZ application ?
Each Oozie action, it encapsulated in Ooize container. Once the oozie action is triggered, 1st the container triggers with oozie configured settings and then the actual executable with overridden settings. This is default behavior of Oozie.
Thus, in your case, Oozie Hive containter was triggered 1st, with TEZ engine. Later when the Hive script got executed, the setting was overridden with MapReduce.
Is this causing any issue/side-effect?
In my case, I set the queue for Oozie container with the following config:
I can see the Oozie Container in the Queue oozie-launcher :
In the queue default, I see 2 applications that I mentioned above, when I change the default Engine on HDP (MR), I see one application on the default queue.
>Is this causing any issue/side-effect?
The application Hive-XXXX occupies every time an container without doing anything.
why when I change the default engine to MR in HDP, I don't see anymore the 3rd application (TEZ) ?
Oozie container with TEZ is created only when the default engine is TEZ even if I do not use it ?