[
https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614882#comment-13614882
]
Hadoop QA commented on YARN-474:
--------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575633/YARN-474.3.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}. The javadoc tool did not generate any
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/613//testReport/
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/613//console
This message is automatically generated.
> CapacityScheduler does not activate applications when
> maximum-am-resource-percent configuration is refreshed
> ------------------------------------------------------------------------------------------------------------
>
> Key: YARN-474
> URL: https://issues.apache.org/jira/browse/YARN-474
> Project: Hadoop YARN
> Issue Type: Bug
> Components: capacityscheduler
> Affects Versions: 2.0.3-alpha, 0.23.6
> Reporter: Hitesh Shah
> Assignee: Zhijie Shen
> Attachments: YARN-474.1.patch, YARN-474.2.patch, YARN-474.3.patch
>
>
> Submit 3 applications to a cluster where capacity scheduler limits allow only
> 1 running application. Modify capacity scheduler config to increase value of
> yarn.scheduler.capacity.maximum-am-resource-percent and invoke refresh
> queues.
> The 2 applications not yet in running state do not get launched even though
> limits are increased.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
