Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Feb 2017 19:43:44 +0000 (UTC)
From: "Yufei Gu (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13043161.1487137513000.34670.1487792624265@Atlassian.JIRA>
In-Reply-To: <JIRA.13043161.1487137513000@Atlassian.JIRA>
References: <JIRA.13043161.1487137513000@Atlassian.JIRA> <JIRA.13043161.1487137513341@jira-lw-us.apache.org>
Subject: [jira] [Commented] (YARN-6194) Cluster capacity in SchedulingPolicy
 is updated only on allocation file reload
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Feb 2017 19:43:48 -0000


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

Yufei Gu commented on YARN-6194:
--------------------------------

Updated the PR. Using FSContext instead of ClusterNodeTracker.

> Cluster capacity in SchedulingPolicy is updated only on allocation file reload
> ------------------------------------------------------------------------------
>
>                 Key: YARN-6194
>                 URL: https://issues.apache.org/jira/browse/YARN-6194
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Yufei Gu
>
> Some of the {{SchedulingPolicy}} methods need cluster capacity which is set using {{#initialize}} today. However, {{initialize()}} is called only on allocation reload. If nodes are added between reloads, the cluster capacity is not considered until the next reload.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org