hadoop-yarn-issues mailing list archives

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

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

MENG DING commented on YARN-4519:
---------------------------------

Yes the race only happens when computing delta resource, and yes it also happens to increase
request.
bq.  If so, can we set delta resource of SchedContainerChangeRequest when we enter decreaseContainer?
I guess whichever way we take, we need to make sure the delta resource is computed in the
scope of a CS lock (i.e., delta resource for decrease request, increase request, and rollback
action)

I can take a shot at working out a patch if nobody is working on that yet.

> 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)

Mime
View raw message