You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/30 20:16:39 UTC

[jira] [Resolved] (MAPREDUCE-1723) Capacity Scheduler should allow configuration of Map & Reduce task slots independently per queue

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved MAPREDUCE-1723.
-----------------------------------------

    Resolution: Won't Fix

This is sort of Won't Fix for 1.x but Fixed for 2.x since there is no longer any idea of M or R task slots. Booray!?

> Capacity Scheduler should allow configuration of Map & Reduce task slots independently per queue
> ------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-1723
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1723
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: capacity-sched
>    Affects Versions: 0.20.1
>         Environment: all
>            Reporter: Subramaniam Venkatraman Krishnan
>
> The Capacity Scheduler allows configuration of percentage of task slots per queue. We have a scenario in which our biggest queue (50% quota) has Jobs with mainly Map tasks & we need to enforce strict capacity limits per queue due to SLA requirements. So other smaller queues which require Reduce tasks gets starved even though the Reduce slots are idle. The Grid can be more efficiently utilized if Capacity Scheduler allows configuration of Map & Reduce task slots capacity independently per queue.



--
This message was sent by Atlassian JIRA
(v6.2#6252)