Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 1 May 2015 13:27:07 +0000 (UTC)
From: "Thomas Graves (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12776992.1424735392000.45841.1430486827441@Atlassian.JIRA>
In-Reply-To: <JIRA.12776992.1424735392000@Atlassian.JIRA>
References: <JIRA.12776992.1424735392000@Atlassian.JIRA>
 <JIRA.12776992.1424735392521@arcas>
Subject: [jira] [Commented] (YARN-3243) CapacityScheduler should pass
 headroom from parent to children to make sure ParentQueue obey its capacity
 limits.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523187#comment-14523187 ] 

Thomas Graves commented on YARN-3243:
-------------------------------------

thanks [~leftnoteasy] I'll attempt to merge YARN-3434. If its not clean I'll put up a patch for it.

> CapacityScheduler should pass headroom from parent to children to make sure ParentQueue obey its capacity limits.
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3243
>                 URL: https://issues.apache.org/jira/browse/YARN-3243
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler, resourcemanager
>            Reporter: Wangda Tan
>            Assignee: Wangda Tan
>             Fix For: 2.8.0
>
>         Attachments: YARN-3243.1.patch, YARN-3243.2.patch, YARN-3243.3.patch, YARN-3243.4.patch, YARN-3243.5.patch
>
>
> Now CapacityScheduler has some issues to make sure ParentQueue always obeys its capacity limits, for example:
> 1) When allocating container of a parent queue, it will only check parentQueue.usage < parentQueue.max. If leaf queue allocated a container.size > (parentQueue.max - parentQueue.usage), parent queue can excess its max resource limit, as following example:
> {code}
>         A  (usage=54, max=55)
>        /     \
>       A1     A2 (usage=1, max=55)
> (usage=53, max=53)
> {code}
> Queue-A2 is able to allocate container since its usage < max, but if we do that, A's usage can excess A.max.
> 2) When doing continous reservation check, parent queue will only tell children "you need unreserve *some* resource, so that I will less than my maximum resource", but it will not tell how many resource need to be unreserved. This may lead to parent queue excesses configured maximum capacity as well.
> With YARN-3099/YARN-3124, now we have {{ResourceUsage}} class in each class, *here is my proposal*:
> - ParentQueue will set its children's ResourceUsage.headroom, which means, *maximum resource its children can allocate*.
> - ParentQueue will set its children's headroom to be (saying parent's name is "qA"): min(qA.headroom, qA.max - qA.used). This will make sure qA's ancestors' capacity will be enforced as well (qA.headroom is set by qA's parent).
> - {{needToUnReserve}} is not necessary, instead, children can get how much resource need to be unreserved to keep its parent's resource limit.
> - More over, with this, YARN-3026 will make a clear boundary between LeafQueue and FiCaSchedulerApp, headroom will consider user-limit, etc.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)