[
https://issues.apache.org/jira/browse/HIVE-22103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943156#comment-16943156
]
Richard Zhang commented on HIVE-22103:
--------------------------------------
This is not a bug, but it is about how to use the priority configure feature.
YARN provides the facility to configure the priority of applications, for
example, users can configure the priority of the application by
yarn application -appId <appid> -updatePriority <priority>
By default, YARN does not specify priority and the default is 0. But users can
use the above facility to assign priority.
When YARN launches the applications. It will first launch the SERVICE AM, next
is TEZ AM. TEZ AM cannot acquire the resources from SERVICE AM in the normal
situation, because they are separate containers.
The corner case will only happen in a single node cluster, where the user’s
cluster lacks resource, where the cluster can not launch more containers when
both SERVICE AM and TEZ AM are demanding for containers. But because YARN
SERVICE AM and the TEZ AM has the same priority, killing YARN service AM does
enable TEZ AM container to launch. Moreover, the use can use the following
configure command to explicitly set the priority.
yarn application -appId <appid> -updatePriority <priority>
The users can setup this in their default config.
So this is not a bug, but it is about how to use the priority configure feature.
> Yarn-Service is not launched with higher priority by HS2
> --------------------------------------------------------
>
> Key: HIVE-22103
> URL: https://issues.apache.org/jira/browse/HIVE-22103
> Project: Hive
> Issue Type: Task
> Components: HiveServer2, llap
> Affects Versions: 3.1.0
> Reporter: Sampada Dehankar
> Assignee: Richard Zhang
> Priority: Major
>
> In Hive 3.x, Yarn-Service is used to launch llap-daemons. If a container
> (llap-daemon) is killed and there are pending Tez AMs, the llap-daemon
> container might not get launched as the available resources can be utilized
> by Tez AMs.
> This happens as Yarn-Service and Tez AMs both are launched with the same Yarn
> Application priority (0). Due to this, which of the two would get the
> resource is uncertain.
> In the previous versions on Hive, this issue was not present as Slider was
> launched with priority 1. And Tez AMs are launched with priority 0.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
