[YARN-4519] potential deadlock of CapacityScheduler between decrease container and assign containers

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.8.0, 3.0.0-alpha1
• Component/s: capacityscheduler
• Target Version/s: 2.8.0
• Hadoop Flags: Reviewed
• Assignee: MENG DING
• Reporter: sandflee
• Created: 28/Dec/15 03:51
• Updated: 30/Aug/16 01:08
• Resolved: 28/Jan/16 22:52

Description

In CapacityScheduler.allocate() , first get FiCaSchedulerApp sync lock, and may be get CapacityScheduler's sync lock in decreaseContainer()
In scheduler thread, first get CapacityScheduler's sync lock in allocateContainersToNode(), and may get FiCaSchedulerApp sync lock in FicaSchedulerApp.assignContainers().

Issue Links

• blocks: YARN-4138 Roll back container resource allocation after resource increase token expires