[
https://issues.apache.org/jira/browse/YARN-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039644#comment-14039644
]
Hadoop QA commented on YARN-2187:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12651785/YARN-2187.patch
against trunk revision .
{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:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler 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 1.3.9) 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.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-YARN-Build/4037//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/4037//console
This message is automatically generated.
> FairScheduler: Disable max-AM-share check by default
> ----------------------------------------------------
>
> Key: YARN-2187
> URL: https://issues.apache.org/jira/browse/YARN-2187
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler
> Affects Versions: 2.5.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: YARN-2187.patch
>
>
> Say you have a small cluster with 8gb memory and 5 queues. This means that
> equal queue can have 8gb / 5 = 1.6gb but an AM requires 2gb to start so no
> AMs can be started. By default, max-am-share check should be disabled so
> users don't see a regression. On medium-sized clusters, it still makes sense
> to set the max-am-share to a value between 0 and 1.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
