[YARN-325] RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.2-alpha, 0.23.5
• Fix Version/s: 2.0.3-alpha, 0.23.6
• Component/s: capacityscheduler
• Assignee: Arun Murthy
• Reporter: Jason Darrell Lowe
• Created: 08/Jan/13 23:28
• Updated: 03/Sep/14 23:25
• Resolved: 09/Jan/13 21:04

Description

If a client calls getQueueInfo on a parent queue (e.g.: the root queue) and containers are completing then the RM can deadlock. getQueueInfo() locks the ParentQueue and then calls the child queues' getQueueInfo() methods in turn. However when a container completes, it locks the LeafQueue then calls back into the ParentQueue. When the two mix, it's a recipe for deadlock.

Stacktrace to follow.