hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandflee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4519) potential deadlock of CapacityScheduler between decrease container and assign containers
Date Tue, 29 Dec 2015 08:11:49 GMT

    [ https://issues.apache.org/jira/browse/YARN-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073622#comment-15073622
] 

sandflee commented on YARN-4519:
--------------------------------

sorry, I don't understand 
1, why should we put compute delta resource under CS lock?
2, why should we put decreaseContainer under CS lock?  
to avoid what race conditions?  thanks.

> 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
>            Assignee: MENG DING
>
> 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)

Mime
View raw message