Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 13 Mar 2014 16:19:52 +0000 (UTC)
From: "Jonathan Eagles (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12698002.1393617676782.60568.1394727592060@arcas>
In-Reply-To: <JIRA.12698002.1393617676782@arcas>
References: <JIRA.12698002.1393617676782@arcas>
Subject: [jira] [Commented] (YARN-1769) CapacityScheduler:  Improve
 reservations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Eagles commented on YARN-1769:
---------------------------------------

Hi, Tom. Can you comment on the findbugs warnings that are introduced as part of this patch when you get a chance?

> CapacityScheduler:  Improve reservations
> ----------------------------------------
>
>                 Key: YARN-1769
>                 URL: https://issues.apache.org/jira/browse/YARN-1769
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 2.3.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>         Attachments: YARN-1769.patch, YARN-1769.patch
>
>
> Currently the CapacityScheduler uses reservations in order to handle requests for large containers and the fact there might not currently be enough space available on a single host.
> The current algorithm for reservations is to reserve as many containers as currently required and then it will start to reserve more above that after a certain number of re-reservations (currently biased against larger containers).  Anytime it hits the limit of number reserved it stops looking at any other nodes. This results in potentially missing nodes that have enough space to fullfill the request.   
> The other place for improvement is currently reservations count against your queue capacity.  If you have reservations you could hit the various limits which would then stop you from looking further at that node.  
> The above 2 cases can cause an application requesting a larger container to take a long time to gets it resources.  
> We could improve upon both of those by simply continuing to look at incoming nodes to see if we could potentially swap out a reservation for an actual allocation. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)