[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-474: - Attachment: YARN-474.2.patch Separate the fix for the specific problem of YARN-474 and that of YARN-209, to make the other issue independent, though the two issues share the same root cause. > CapacityScheduler does not activate applications when 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
[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhijie Shen updated YARN-474: - Attachment: YARN-474.1.patch According to my investigation, the problem is that the applications in the pending list are only activated when application is added or removed. In contrast, when the metrics of a queue is updated (triggered by either refreshing configuration or updating cluster resource), the application activation function will not be called. So the solution is obviously that when the queue metrics are updated, we need to activate the pending applications if possible. Please have a look at the patch for the details. It also includes the corresponding tests. > CapacityScheduler does not activate applications when 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 > > > 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
[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-474: - Assignee: Zhijie Shen > CapacityScheduler does not activate applications when 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 > > 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
[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated YARN-474: --- Target Version/s: 0.23.7, 2.0.5-beta (was: 2.0.5-beta) Affects Version/s: 2.0.3-alpha 0.23.6 > CapacityScheduler does not activate applications when 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 > > 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
[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-474: - Target Version/s: 2.0.5-beta > CapacityScheduler does not activate applications when configuration is > refreshed > > > Key: YARN-474 > URL: https://issues.apache.org/jira/browse/YARN-474 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Reporter: Hitesh Shah > > 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
[jira] [Updated] (YARN-474) CapacityScheduler does not activate applications when configuration is refreshed
[ https://issues.apache.org/jira/browse/YARN-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitesh Shah updated YARN-474: - Component/s: capacityscheduler > CapacityScheduler does not activate applications when configuration is > refreshed > > > Key: YARN-474 > URL: https://issues.apache.org/jira/browse/YARN-474 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler >Reporter: Hitesh Shah > > 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
