hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed
Date Tue, 26 Mar 2013 23:07:15 GMT

     [ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vinod Kumar Vavilapalli updated YARN-474:
-----------------------------------------

    Summary: CapacityScheduler does not activate applications when maximum-am-resource-percent
configuration is refreshed  (was: CapacityScheduler does not activate applications when configuration
is refreshed)
    
> 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
>
>
> 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

Mime
View raw message