[YARN-3277] Queue's current-max-limit should be updated before allocate reserved container.

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: capacityscheduler, resourcemanager
• Assignee: Wangda Tan
• Reporter: Wangda Tan
• Created: 27/Feb/15 19:50
• Updated: 27/Feb/15 19:53

Description

This is introduced by changes of YARN-3265. With YARN-2008, when RM allocates reserved container, it goes to LeafQueue directly, then goes up to root to get LeafQueue's current-max-limit correct. Now we will not go up, so LeafQueue cannot get maxQueueLimit updated before allocating reserved container.

One possible solution is, we can still start from root when allocate reserved container, but goes to LeafQueue which reserved container belongs to from top to bottom.

Issue Links

• depends upon: YARN-3265 CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)
• is blocked by: YARN-3265 CapacityScheduler deadlock when computing absolute max avail capacity (fix for trunk/branch-2)