hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xieguiming (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
Date Wed, 25 Apr 2012 04:22:52 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13261290#comment-13261290
] 

xieguiming commented on MAPREDUCE-4124:
---------------------------------------

Robert, you are right. the schedulers do not use the priority currently. 
I think we can change the FIFOschedulers to support the priority firstly.
Currently, the FIFOschedulers only sort by submiting time. and we can change 
to sort by priority firstly, and then by submiting time.
 
                
> 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

        

Mime
View raw message