hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-1398) Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner call
Date Thu, 20 Feb 2014 22:51:24 GMT

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

Vinod Kumar Vavilapalli updated YARN-1398:
------------------------------------------

    Attachment: YARN-1398-20140220.txt

Here's a patch that reverts the behavior to be same as before YARN-569. Updating the parent-queue
_outside_ of leaf-queue lock.

Don't think I can write any unit tests for this..

> Deadlock in capacity scheduler leaf queue and parent queue for getQueueInfo and completedConatiner
call
> -------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-1398
>                 URL: https://issues.apache.org/jira/browse/YARN-1398
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.2.0
>            Reporter: Sunil G
>            Priority: Blocker
>         Attachments: YARN-1398-20140220.txt
>
>
> getQueueInfo in parentQueue will call  child.getQueueInfo().
> This will try acquire the leaf queue lock over parent queue lock.
> Now at same time if a completedContainer call comes and acquired LeafQueue lock and it
will wait for ParentQueue's completedConatiner call.
> This lock usage is not in synchronous and can lead to deadlock.
> With JCarder, this is showing as a potential deadlock scenario.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message