[ 
https://issues.apache.org/jira/browse/HIVE-15444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254765#comment-17254765
 ] 

Oleksiy Sayankin commented on HIVE-15444:
-----------------------------------------

These are results of verification of 
[HIVE-14397|https://issues.apache.org/jira/browse/HIVE-14397] with disabled 
queue name removal via {{hive.server2.tez.unset.tez.queue.name = false}}
{code}
conf.unset(TezConfiguration.TEZ_QUEUE_NAME)
{code}
 statement.


*1.*

Configure Hive on Tez.

*2.*

Configure in {{hive-site.xml}}

{code}
<property>
    <name>hive.server2.tez.unset.tez.queue.name</name>
    <value>false</value>
  </property>

<property>
    <name>hive.server2.tez.default.queues</name>
    <value>q1,q2</value>
  </property>
{code}

Here we define two queues for Tez jobs: q1 and q2. We also disable removing Tez 
queue name after query execution.

*3.*

Configure in {{tez-site.xml}}

{code}
   <property>
        <name>tez.session.am.dag.submit.timeout.secs</name>
        <value>60</value>
    </property>
{code}

This property allows to set Tez session timeout to 60 seconds.

*4.*

In console 1: run Beeline, connect to HS2 and set

{code}
0: jdbc:hive2://node1.cluster.com:10000/defau> set tez.queue.name=q1;
{code}

*5.*

In console 2: run Beeline, connect to HS2 and set

{code}
0: jdbc:hive2://node1.cluster.com:10000/defau> set tez.queue.name=q2;
{code}


*6.*

In console 1: run any simple query that triggers Tez job
{code}
0: jdbc:hive2://node1.cluster.com:10000/defau> select sum(id) from test;
{code}

*7.*

In console 2: run any simple query that triggers Tez job
{code}
0: jdbc:hive2://node1.cluster.com:10000/defau> select sum(id) from test;
{code}

*8.*

See two YARN applications: each for a queue: q1 and q2.

{code}
[myuser@node1 ~]$ yarn application -list
{code}

{code}
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):2
                Application-Id      Application-Name        Application-Type    
      User           Queue                   State             Final-State      
       Progress                        Tracking-URL
application_1608718387253_0011  HIVE-e5b114cc-5b31-465e-9204-3b49daf71038       
                 TEZ          myuser       root.q2                 RUNNING      
         UNDEFINED                   0%  http://node1.cluster.com:46621/ui/
application_1608718387253_0012  HIVE-b307590b-1fe6-445c-bf6b-57e72d88d92d       
                 TEZ          myuser       root.q1                 RUNNING      
         UNDEFINED                   0%  http://node1.cluster.com:42410/ui/
{code}

*9.*

Wait for 60 seconds ans see that Tez sessions are expired

{code}
[myuser@node1 ~]$ yarn application -list
{code}

{code}
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):0
                Application-Id      Application-Name        Application-Type    
      User           Queue                   State             Final-State      
       Progress                        Tracking-URL
[myuser@node1 ~]$ 
{code}

*10.*

Run queries from console 1 and 2 and check that there is no 4 YARN applications 
 after that:

{code}
[myuser@node1 ~]$ yarn application -list
{code}

{code}
Total number of applications (application-types: [] and states: [SUBMITTED, 
ACCEPTED, RUNNING]):2
                Application-Id      Application-Name        Application-Type    
      User           Queue                   State             Final-State      
       Progress                        Tracking-URL
application_1608718387253_0011  HIVE-e5b114cc-5b31-465e-9204-3b49daf71038       
                 TEZ          myuser       root.q2                 RUNNING      
         UNDEFINED                   0%  http://node1.cluster.com:46621/ui/
application_1608718387253_0012  HIVE-b307590b-1fe6-445c-bf6b-57e72d88d92d       
                 TEZ          myuser       root.q1                 RUNNING      
         UNDEFINED                   0%  http://node1.cluster.com:42410/ui/
{code}

*RESOLUTION*

We did not observe 
[HIVE-14397|https://issues.apache.org/jira/browse/HIVE-14397] after applying 
the fix.

> tez.queue.name is invalid after tez job running on CLI
> ------------------------------------------------------
>
>                 Key: HIVE-15444
>                 URL: https://issues.apache.org/jira/browse/HIVE-15444
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.1.1, 2.2.0
>            Reporter: Hui Fei
>            Assignee: Oleksiy Sayankin
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.2.0
>
>         Attachments: HIVE-15444.1.patch, HIVE-15444.2.patch
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {code}
> hive> set tez.queue.name;
> tez.queue.name is undefined
> hive> set tez.queue.name=HQ_OLPS;
> hive> set tez.queue.name;
> tez.queue.name=HQ_OLPS
> {code}
> {code}
> hive> insert into abc values(2,2);
> Query ID = hadoop_20161216181208_6c382e49-ac4a-4f52-ba1e-3ed962733fc1
> Total jobs = 1
> Launching Job 1 out of 1
> Status: Running (Executing on YARN cluster with App id 
> application_1481877998678_0011)
> ----------------------------------------------------------------------------------------------
>         VERTICES      MODE        STATUS  TOTAL  COMPLETED  RUNNING  PENDING  
> FAILED  KILLED
> ----------------------------------------------------------------------------------------------
> Map 1 .......... container     SUCCEEDED      1          1        0        0  
>      0       0
> ----------------------------------------------------------------------------------------------
> VERTICES: 01/01  [==========================>>] 100%  ELAPSED TIME: 6.57 s
> ----------------------------------------------------------------------------------------------
> Loading data to table default.abc
> OK
> Time taken: 19.983 seconds
> {code}
> {code}
> hive> set tez.queue.name;
> tez.queue.name is undefined
> hive> set hive.execution.engine;
> hive.execution.engine=tez
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to