[
https://issues.apache.org/jira/browse/MAPREDUCE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728210#action_12728210
]
Hudson commented on MAPREDUCE-516:
----------------------------------
Integrated in Hadoop-Mapreduce-trunk #15 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/15/])
> Fix the 'cluster drain' problem in the Capacity Scheduler wrt High RAM Jobs
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-516
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-516
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.1
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.21.0
>
> Attachments: HADOOP-5964-11.patch, HADOOP-5964-12.patch,
> HADOOP-5964_0_20090602.patch, HADOOP-5964_10_20090622.patch,
> HADOOP-5964_11_20090623.patch, HADOOP-5964_1_20090608.patch,
> HADOOP-5964_1_20090623_yhadoop.patch, HADOOP-5964_2_20090609.patch,
> HADOOP-5964_2_20090629_yhadoop.patch, HADOOP-5964_2_20090629_yhadoop.patch,
> HADOOP-5964_4_20090615.patch, HADOOP-5964_6_20090617.patch,
> HADOOP-5964_7_20090618.patch, HADOOP-5964_8_20090618.patch,
> HADOOP-5964_9_20090619.patch, HADOOP-5964_9_20090619.patch,
> MAPREDUCE-516-Y20.patch
>
>
> When a HighRAMJob turns up at the head of the queue, the current
> implementation of support for HighRAMJobs in the Capacity Scheduler has
> problem in that the scheduler stops assigning tasks to all TaskTrackers in
> the cluster until a HighRAMJob finds a suitable TaskTrackers for all its
> tasks.
> This causes a severe utilization problem since effectively no new tasks are
> allowed to run until the HighRAMJob (at the head of the queue) gets slots.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
