CapacityScheduler should have prevent a single job taking over large parts of a
cluster
---------------------------------------------------------------------------------------
Key: MAPREDUCE-1485
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1485
Project: Hadoop Map/Reduce
Issue Type: Improvement
Components: contrib/capacity-sched
Reporter: Arun C Murthy
Assignee: Arun C Murthy
Fix For: 0.22.0
The proposal is to have a per-queue limit on the number of concurrent tasks a
job can run on a cluster.
We've seen cases where a single, large, job took over a majority of the cluster
- worse, it meant that any bug in it caused issues for both the NameNode _and_
the JobTracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
