[
https://issues.apache.org/jira/browse/MAPREDUCE-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737076#comment-14737076
]
Eric Payne commented on MAPREDUCE-5870:
---------------------------------------
{quote}
There's only two ways I can currently think of to get around that. Either we
need to obsolete the priority field from the job status and provide a separate
call to get the priority when the client really wants to know it, or we have to
find a way for the AM to know its job priority so it can return it in its
JobStatus responses. For the latter we could have the RM send it down in
heartbeat responses, but there would be a delay between when a client updates
the priority and the AM reports the updated value.
{quote}
[~jlowe] and [~sunilg],
I would vote for the second option. That is, update the priority in the RM and
then tell the AM about it when it hearbeats in. I think it would be fine to
have the short delay between when the priority was updated and the AM knows
about it. I can't foresee a use case where the client would atomically need to
know about the change. The one thing that might cause confusion is if the
client set the priority and immediately read the priority which might still be
the old value. This may cause confusion, but as long as this behavior is well
documented it should be fine.
> 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)
