[
https://issues.apache.org/jira/browse/TEZ-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639302#comment-14639302
]
Hitesh Shah commented on TEZ-2627:
----------------------------------
Comments:
- do not set priority if not defined in config. i.e.
TEZ_APPLICATION_PRIORITY_DEFAULT should not exist. Let YARN figure out what it
wants to do if an app priority is not provided.
- Minor nit on the config name: lets call it "tez.am.application.priority" -
"tez.am" denotes AM specific value and "application.priority" is pretty clear
to understand by itself. Field name should change to
TEZ_AM_APPLICATION_PRIORITY as a result.
- For the unit tests, why are IOException and YARNExceptions being caught?
Shouldn't the test fail if an exception is thrown?
- Might be useful to update say TestTezJobs to set app priority to +1 for
one of the jobs that runs against MiniYARNCluster ( not all of the jobs though
so that both cases are covered ).
> 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.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)
