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

Subramaniam Krishnan updated MAPREDUCE-1723:
--------------------------------------------

        Summary: Capacity Scheduler should allow configuration of Map & Reduce 
task slots independently per queue  (was: Capacity Scheduler should allow 
configuration of Map & Reduce task slots independantly )
     Issue Type: Improvement  (was: Bug)
    Description: 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.  (was: The JobTracker UI shows 
both Failed/Killed Jobs as Failed. The Killed job status has been separated 
from Failed as part of HADOOP-3924, so the UI needs to be updated to reflect 
the same.
)
    Component/s: contrib/capacity-sched
                     (was: jobtracker)

> 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: contrib/capacity-sched
>    Affects Versions: 0.20.1
>         Environment: all
>            Reporter: Subramaniam Krishnan
>             Fix For: 0.20.3
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to