[YARN-11648] CapacityScheduler does not activate applications when resources are released from another Leaf Queue

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: capacity scheduler
• Assignee: Unassigned
• Reporter: Brian Goerlitz
• Created: 18/Jan/24 22:28
• Updated: 18/Jan/24 22:39

Description

Create a queue with low minimum capacity and high maximum capacity. If multiple apps are submitted to the queue such that the Queue's Max AM resource limit is exceeded while other cluster resources are consumed by different queues, these apps will not be considered for activation when cluster resources from the other queues are freed. As the AM limit is calculated based on available resources for the queue, these apps should be activated.