[ 
https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sandflee updated YARN-4519:
---------------------------
    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(). 

  was:
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. 


> potential deadlock of CapacityScheduler between decrease container and assign 
> containers
> ----------------------------------------------------------------------------------------
>
>                 Key: YARN-4519
>                 URL: https://issues.apache.org/jira/browse/YARN-4519
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>            Reporter: sandflee
>
> 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(). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to