[
https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275104#comment-14275104
]
Hudson commented on YARN-3027:
------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #806 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/806/])
YARN-3027. Scheduler should use totalAvailable resource from node instead of
availableResource for maxAllocation. (adhoot via rkanter) (rkanter: rev
ae7bf31fe1c63f323ba5271e50fd0e4425a7510f)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/AbstractYarnScheduler.java
* hadoop-yarn-project/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/TestAbstractYarnScheduler.java
> Scheduler should use totalAvailable resource from node instead of
> availableResource for maxAllocation
> -----------------------------------------------------------------------------------------------------
>
> Key: YARN-3027
> URL: https://issues.apache.org/jira/browse/YARN-3027
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Anubhav Dhoot
> Assignee: Anubhav Dhoot
> Fix For: 2.7.0
>
> Attachments: YARN-3027.001.patch, YARN-3027.002.patch
>
>
> YARN-2604 added support for updating maxiumum allocation resource size based
> on nodes. But it incorrectly uses available resource instead of maximum
> resource.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
