You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Dénes Bodó (Jira)" <ji...@apache.org> on 2021/12/02 09:55:00 UTC

[jira] [Created] (OOZIE-3643) Oozie should pass mapreduce.job.tags to Beeline in Hive2 action

Dénes Bodó created OOZIE-3643:
---------------------------------

             Summary: Oozie should pass mapreduce.job.tags to Beeline in Hive2 action
                 Key: OOZIE-3643
                 URL: https://issues.apache.org/jira/browse/OOZIE-3643
             Project: Oozie
          Issue Type: Task
    Affects Versions: 5.2.1
            Reporter: Dénes Bodó


Currently if we start a Hive2 action which starts a Tez child job and that runs for long and then we try to kill the Oozie workflow which started that Hive2 action we experience that the started Tez child job remains running.

To solve this problem Hive on Tez configurations should be set: *hive.server2.tez.initialize.default.sessions=false* and Oozie should pass the launcher job's tag to beeline to be able to find the Tez child job. In Oozie we could do something like:
{code:java}
arguments.add("--hiveconf");
arguments.add("hive.query.tag=" + actionConf.get(MAPREDUCE_JOB_TAGS)); {code}
in Hive2Main class.

As I experienced in my test environment when I did killed such a workflow it killed the Tez child job too but unfortunately a new instance of my workflow wasn't able to start the Hive query, the launcher job stuck.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)