[
https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615052#comment-13615052
]
Hadoop QA commented on YARN-474:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12575682/YARN-474.4.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/616//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
> Fix For: 2.0.5-beta
>
> Attachments: YARN-474.1.patch, YARN-474.2.patch, YARN-474.3.patch,
> YARN-474.4.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
