[
https://issues.apache.org/jira/browse/YARN-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985485#comment-13985485
]
Jason Lowe commented on YARN-2002:
----------------------------------
Moving this to MAPREDUCE since that's where the changes need to be made. Will
link this issue back to YARN-1963.
I think a small unit test should be added as part of this change to verify that
when a priority is set the resulting submission context from YARNRunner has the
appropriate priority setting. I suspect the tests in YARN-2004 will be more of
an integration test rather than a unit test.
> Support for passing Job priority through Application Submission Context in
> Mapreduce Side
> -----------------------------------------------------------------------------------------
>
> Key: YARN-2002
> URL: https://issues.apache.org/jira/browse/YARN-2002
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, resourcemanager
> Reporter: Sunil G
> Attachments: Yarn-2002.1.patch
>
>
> Job Prioirty can be set from client side as below [Configuration and api].
> a. JobConf.getJobPriority() and
> Job.setPriority(JobPriority priority)
> b. We can also use configuration
> "mapreduce.job.priority".
> Now this Job priority can be passed in Application Submission
> context from Client side.
> Here we can reuse the MRJobConfig.PRIORITY configuration.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
