[YARN-2008] CapacityScheduler may report incorrect queueMaxCap if there is hierarchy queue structure

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.6.0
• Target Version/s: 2.6.0
• Hadoop Flags: Reviewed
• Assignee: Craig Welch
• Reporter: Chen He
• Created: 30/Apr/14 16:14
• Updated: 24/Feb/15 15:27
• Resolved: 07/Aug/14 20:02

Description

If there are two queues, both allowed to use 100% of the actual resources in the cluster. Q1 and Q2 currently use 50% of actual cluster's resources and there is not actual space available. If we use current method to get headroom, CapacityScheduler thinks there are still available resources for users in Q1 but they have been used by Q2.
If the CapacityScheduelr has a hierarchy queue structure, it may report incorrect queueMaxCap. Here is a example

	rootQueue
	/	\
L1ParentQueue1		L1ParentQueue2
(allowed to use up 80% of its parent)		(allowed to use 20% in minimum of its parent)
/	\
L2LeafQueue1	L2LeafQueue2
(50% of its parent)	(50% of its parent in minimum)

When we calculate headroom of a user in L2LeafQueue2, current method will think L2LeafQueue2 can use 40% (80%*50%) of actual rootQueue resources. However, without checking L1ParentQueue1, we are not sure. It is possible that L1ParentQueue2 have used 40% of rootQueue resources right now. Actually, L2LeafQueue2 can only use 30% (60%*50%).

Issue Links

• breaks: YARN-3251 Fix CapacityScheduler deadlock when computing absolute max avail capacity (short term fix for 2.6.1)