[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14641360#comment-14641360
]
Sunil G commented on MAPREDUCE-5870:
------------------------------------
Thank you [~jianhe] for review and sharing the comments.
I have looked into the test failures and analyzed the problem. It seems we
still have implementation of old MRV1 priority in code.
{code}
@InterfaceAudience.Public
@InterfaceStability.Stable
public enum JobPriority {
VERY_HIGH,
HIGH,
NORMAL,
LOW,
VERY_LOW;
}
{code}
This enum is used in many places in code. Also we have some stable apis in
JobConf related to JobPriority.
{code}
public void setJobPriority(JobPriority prio)
public JobPriority getJobPriority()
{code}
Do we still need to keep any backward compatibility support to this? If so, we
can do a type convert for this macro and set priority accordingly in
YarnRunner. Otherwise we may need to remove some of unused test cases from MR
related to old way of setting priority.
Kindly advice.
> 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)
