[
https://issues.apache.org/jira/browse/TEZ-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635778#comment-14635778
]
Hitesh Shah commented on TEZ-2627:
----------------------------------
Is the setPriority api on AppSubmissionContext present in all versions of
hadoop > 2.2.0?
If yes, then a new config, "tez.am.app-priority" or simply "tez.am.priority"
should be good enough to be introduced and passed through to the app submission
context creation layer. If not, a shim will be needed.
Are there any valid ranges for the priority? Or does YARN throw back an error
if there is an issue? Does that error handling need to be special cased or is
the exception thrown back clear enough that it can be sent back to the user?
> 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
>
> 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)
