Queue Management with Hive-on-Tez

HiveServer2 provides built-in functionality to set-up and handle a pool of Tez sessions in default queues. Tez initiates a session and keeps it alive to run sequential queries. Quereies can be submitted through HiveServer2 clients, such as Beeline and the Hive CLI. You can manage queues through properties in hive-site.xml.

Queue management is strongly connected to the type of YARN Scheduler used. By default, a MapR cluster uses Fair Scheduler and Hive-on-Tez to run queries in queues with a user name. If a query is submitted from the Hive CLI, the real user name is used. If a query is submitted from a HiveServer2 client, such as Beeline, the queue name depends on the HiveServer2 impersonation configuration property, hive.server2.enable.doAs, where the queue name could be the real user name or the user name of the Hiveserver2 process.

With Capacity Scheduler, Hive queries submitted from the CLI and Beeline are configured through the capacity-scheduler.xml file. Default queue names are chosen from the scheduler settings, but you can also use the tez.queue.name=<queue_name> property to run queries in a specific queue.

set tez.queue.name=<queue_name>;

<property>
   <name>tez.queue.name</name>
   <value>my_queue</value>
</property> 

<property>
   <name>tez.queue.name</name>
   <value>my_queue</value>
</property> 
<property>
    <name>hive.server2.tez.unset.tez.queue.name</name>
    <value>false</value>
</property>