[
https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615208#comment-13615208
]
Hudson commented on YARN-474:
-----------------------------
Integrated in Hadoop-Hdfs-trunk #1357 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1357/])
YARN-474. Fix CapacityScheduler to trigger application-activation when
am-resource-percent configuration is refreshed. Contributed by Zhijie Shen.
(Revision 1461402)
Result = FAILURE
vinodkv :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1461402
Files :
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestLeafQueue.java
> 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
