Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Mon, 27 Apr 2015 18:24:48 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12721787.1403040573000.40832.1430159088198@Atlassian.JIRA>
In-Reply-To: <JIRA.12721787.1403040573000@Atlassian.JIRA>
References: <JIRA.12721787.1403040573000@Atlassian.JIRA>
 <JIRA.12721787.1403040573527@arcas>
Subject: [jira] [Resolved] (YARN-2176) CapacityScheduler loops over all
 running applications rather than actively requesting apps
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe resolved YARN-2176.
------------------------------
    Resolution: Duplicate

OK, we'll use YARN-3547 for the FairScheduler.  Resolving this as fixed by YARN-3361.

> CapacityScheduler loops over all running applications rather than actively requesting apps
> ------------------------------------------------------------------------------------------
>
>                 Key: YARN-2176
>                 URL: https://issues.apache.org/jira/browse/YARN-2176
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>    Affects Versions: 2.4.0
>            Reporter: Jason Lowe
>
> The capacity scheduler performance is primarily dominated by LeafQueue.assignContainers, and that currently loops over all applications that are running in the queue.  It would be more efficient if we looped over just the applications that are actively asking for resources rather than all applications, as there could be thousands of applications running but only a few hundred that are currently asking for resources.


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