[
https://issues.apache.org/jira/browse/YARN-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14272172#comment-14272172
]
Hadoop QA commented on YARN-3027:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12691427/YARN-3027.001.patch
against trunk revision 8c3e888.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:red}-1 javac{color}. The applied patch generated 1217 javac
compiler warnings (more than the trunk's current 1214 warnings).
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/6295//testReport/
Javac warnings:
https://builds.apache.org/job/PreCommit-YARN-Build/6295//artifact/patchprocess/diffJavacWarnings.txt
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/6295//console
This message is automatically generated.
> 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
> Attachments: YARN-3027.001.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)
