[
https://issues.apache.org/jira/browse/YARN-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872805#comment-15872805
]
ASF GitHub Bot commented on YARN-6194:
--------------------------------------
GitHub user flyrain opened a pull request:
https://github.com/apache/hadoop/pull/196
YARN-6194. Cluster capacity in SchedulingPolicy is updated only on
allocation file reload
This patch passes the ClusterNodeTracker instead of ClusterResource into
the DRF policy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/flyrain/hadoop yarn-6194
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/196.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #196
----
commit 78c6303b15d5531fc0bd22331a0720803ad5c416
Author: Yufei Gu <yufei...@cloudera.com>
Date: 2017-02-17T23:57:11Z
YARN-6194. Cluster capacity in SchedulingPolicy is updated only on
allocation file reload.
----
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
