[
https://issues.apache.org/jira/browse/HADOOP-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647277#action_12647277
]
Vivek Ratan commented on HADOOP-4558:
-------------------------------------
It's true that queue information is updated at the beginning of assignTasks().
It can be done at the end too, but it won't help much. In fact, we may call
updateQSIObjects() once every few heartbeats, if the call is expensive. Any
code that requires exact information about the state of the queues should call
updateQSIObjects() and should not rely on when this method is called by
assignTasks(). Hence, a better solution is for reclaimCapacity() to call
updateQSIObjects() at the beginning.
> 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
> Assignee: Amar Kamat
> Attachments: 4558.1.patch, HADOOP-4558-v1.4.patch
>
>
> 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.
