[YARN-474] CapacityScheduler does not activate applications when maximum-am-resource-percent configuration is refreshed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.3-alpha, 0.23.6
• Fix Version/s: 2.1.0-beta
• Component/s: capacityscheduler
• Target Version/s: 0.23.7, 2.1.0-beta
• Hadoop Flags: Reviewed
• Assignee: Zhijie Shen
• Reporter: Hitesh Shah
• Created: 13/Mar/13 21:29
• Updated: 27/Aug/13 22:15
• Resolved: 27/Mar/13 17:45

Description

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.

Issue Links

• blocks: YARN-209 Capacity scheduler doesn't trigger app-activation after adding nodes