You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2015/07/13 16:33:05 UTC
[jira] [Updated] (MAPREDUCE-5870) Support for passing Job priority
through Application Submission Context in Mapreduce Side
[ https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunil G updated MAPREDUCE-5870:
-------------------------------
Attachment: 0001-MAPREDUCE-5870.patch
Uploading an updated version of patch with test case.
In YARN, if a client is not setting application priority in its submission context, then default priority from queue is considered.
Hence in MR, I did not set any default priority if user is not specifying priority in {{mapreduce.job.priority}}. Please share thoughts.
> Support for passing Job priority through Application Submission Context in Mapreduce Side
> -----------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-5870
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5870
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-MAPREDUCE-5870.patch, 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.3.4#6332)