[
https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261930#comment-13261930
]
Robert Joseph Evans commented on MAPREDUCE-4124:
------------------------------------------------
I am fine with making sure that the priority information is passed up to the
scheduler, and if you want to update the FIFO scheduler to go off of priority
as well I don't see much of an issue with that either. But for any other
scheduler I would like to see that work done as a separate JIRA because it is
likely to be a lot of work, and may be somewhat controversial.
> Job Priority is not changing
> -----------------------------
>
> Key: MAPREDUCE-4124
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4124
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 3.0.0
> Reporter: Nishan Shetty
> Priority: Critical
>
> 1.Submit job
> 2.Change the job priority using setPriority() or CLI command ./mapred
> job-set-priority <job-id> <priority>
> Observe that Job priority is not changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
