[
https://issues.apache.org/jira/browse/HADOOP-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644672#action_12644672
]
Vivek Ratan commented on HADOOP-4558:
-------------------------------------
The Capacity Scheduler updates its queue-based data structures on every
heartbeat, when a task needs to be assigned. What happened here was that a job
was submitted, but all TTs were running long-running maps and no call to
assignTasks() was made. Hence the Scheduler never updated its structures and
was unaware of the 2nd job being added. It's a fairly simple fix - update the
data structure when a job is added/removed.
> Scheduler fails to reclaim capacity if Jobs are submitted to queue one after
> the other
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-4558
> URL: https://issues.apache.org/jira/browse/HADOOP-4558
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Affects Versions: 0.19.0
> Environment: Cluster Capacity Maps=Reduces =210 each
> Two Queues:
> Q1: default, GC (%) =40, GC=84 (Maps and Reduces each). Reclaim time = 3
> mins.
> Q2: test_q1, GC (%) =60, GC=126 (Maps and Reduces each) Reclaim time = 2 mins
> Reporter: Karam Singh
>
> Scheduler fails to reclaim capacity if Jobs are submitted to queue one after
> the other.
> First job submitted with tasks equal to cluster's M/R Capacity
> Second is submitted to different queue when all tasks of First Job are
> running, scheduler fails to reclaim capacity for second job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
