[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14703060#comment-14703060
]
Jason Lowe commented on MAPREDUCE-5870:
---------------------------------------
bq. But now YARN has the capability to take default value, if priority is not
set from client side.
That's exactly what I intended for the new DEFAULT enum to indicate. If set on
the client side then the job submitter shouldy avoid setting any job priority
and let the cluster set an automatic value. In other words, this specific enum
value should be treated as if there was no conf property set.
bq. So I can make 0 as DEFAULT (new enum)
Note that we should not treat a priority of 0 as DEFAULT. As I mentioned
above, DEFAULT means there is no explicit priority set, so no integer priority
value should map to the DEFAULT enum.
bq. I agree with your idea of having a new enum which can be returned when any
other integer is been used a priority other than standard enum.
My main complaint with that approach is that it's not symmetric. That enum
value cannot be set by clients, and it should be treated as an error since we
cannot know which integer priority corresponds. But at least it keeps the
getJobPriority call from crashing, and I don't know of a better approach
offhand.
> 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, 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)
