hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4124) Job Priority is not changing
Date Tue, 24 Apr 2012 14:13:35 GMT

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

Robert Joseph Evans commented on MAPREDUCE-4124:
------------------------------------------------

I thought that the problem was deeper then that.  I do not believe that any of the schedulers
actually use the priority currently, so even just getting the priority over to the RM will
not really do anything yet, at least not until the schedulers are updated to use priority.
                
> 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