[
https://issues.apache.org/jira/browse/TEZ-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639928#comment-14639928
]
Hitesh Shah commented on TEZ-2627:
----------------------------------
I was thinking of code changing only in TezClientUtils. Something along these
lines:
{code}
if ( amConf.getTezConf().get(AM_PRIO) != null) { // isEmpty() check needed
if Integer.parseInt used
int prio = amConf.getTezConf().get(AM_PRIO, 0); // 0 will never be
used as conf string is non-null
submissionCtxt.setPriority(prio);
}
{code}
There are a couple of things to note - Configuration::getInt() only uses the
default if prop value is null. The code above could be changed to use
Integer.parseInt() instead of relying impl behavior of Conf::getInt().
> Support for Tez Job Priorities
> ------------------------------
>
> Key: TEZ-2627
> URL: https://issues.apache.org/jira/browse/TEZ-2627
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Saikat
> Assignee: Saikat
> Attachments: TEZ-2627.1.patch, TEZ-2627.2.patch, TEZ-2627.patch
>
>
> When a Tez Job is submitted via TezClient, an ApplicationSubmissionContext is
> created before submitting the job. ApplicationSubmissionContext has a
> priority field which can be used to provide a priority for the job.
> There is an ongoing effort in the Yarn Community to enable application
> priorities(https://issues.apache.org/jira/browse/YARN-1963).
> https://issues.apache.org/jira/browse/YARN-2003 implements the necessary
> changes in RM and Capacity Scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
