hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3251) CapacityScheduler deadlock when computing absolute max avail capacity
Date Tue, 24 Feb 2015 15:23:04 GMT

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

Jason Lowe commented on YARN-3251:
----------------------------------

It looks like this is fallout from YARN-2008.  CSQueueUtils.getAbsoluteMaxAvailCapacity is
called with the lock held on the LeafQueue and walks up the tree, attempting to grab locks
on parents as it goes.  That's contrary to the conventional order of locking while walking
down the tree, and thus we can deadlock.

> CapacityScheduler deadlock when computing absolute max avail capacity
> ---------------------------------------------------------------------
>
>                 Key: YARN-3251
>                 URL: https://issues.apache.org/jira/browse/YARN-3251
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>            Priority: Blocker
>
> The ResourceManager can deadlock in the CapacityScheduler when computing the absolute
max available capacity for user limits and headroom.



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

Mime
View raw message