[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14743954#comment-14743954
]
Jason Lowe commented on MAPREDUCE-5870:
---------------------------------------
I honestly don't know how much the priority APIs were used from MRv1. However
given that there were priority APIs in MRv1 that's the most logical thing
people migrating from Hadoop 1 will expect to use when they hear priorities are
finally working in Hadoop 2.
If we decide to deprecate the old MRv1 priority API, should we avoid using
mapreduce.job.priority (was mapred.job.priority)? Wondering if jobs that were
working in Hadoop 2 suddenly start failing during job submit because someone
was specifying something for that property that was always ignored and now the
new code barfs on any non-integer found there. However I'm not excited about
the confusion of having two similar properties to set the job priority, one
that works and one that does not.
> 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, 0002-MAPREDUCE-5870.patch,
> 0003-MAPREDUCE-5870.patch, 0004-MAPREDUCE-5870.patch,
> 0005-MAPREDUCE-5870.patch, 0006-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)
