hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Tryuber (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3859) CapacityScheduler incorrectly utilizes extra-resources of queue for high-memory jobs
Date Wed, 15 Feb 2012 10:21:00 GMT

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

Sergey Tryuber commented on MAPREDUCE-3859:
-------------------------------------------

Arun, no, that's not 'user-limit-factor' issue(( This option perfectly works in case if job
consumes only 1 slot per task and we've been using this option for a while. This bug affects
only cases if job consumes more than one slot per task.

Harsh, what version should I try to patch? Is it branch-1.0? Or trunk too?
                
> CapacityScheduler incorrectly utilizes extra-resources of queue for high-memory jobs
> ------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3859
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3859
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/capacity-sched
>    Affects Versions: 1.0.0
>         Environment: CDH3u1
>            Reporter: Sergey Tryuber
>
> Imagine, we have a queue A with capacity 10 slots and 20 as extra-capacity, jobs which
use 3 map slots will never consume more than 9 slots, regardless how many free slots on a
cluster.

--
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