hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Graves (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-325) RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing
Date Wed, 09 Jan 2013 15:48:12 GMT

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

Thomas Graves updated YARN-325:
-------------------------------

    Attachment: YARN-325-branch23.patch
    
> RM CapacityScheduler can deadlock when getQueueInfo() is called and a container is completing
> ---------------------------------------------------------------------------------------------
>
>                 Key: YARN-325
>                 URL: https://issues.apache.org/jira/browse/YARN-325
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.0.2-alpha, 0.23.5
>            Reporter: Jason Lowe
>            Assignee: Arun C Murthy
>            Priority: Blocker
>         Attachments: YARN-325-branch23.patch, YARN-325.patch, YARN-325.patch
>
>
> If a client calls getQueueInfo on a parent queue (e.g.: the root queue) and containers
are completing then the RM can deadlock.  getQueueInfo() locks the ParentQueue and then calls
the child queues' getQueueInfo() methods in turn.  However when a container completes, it
locks the LeafQueue then calls back into the ParentQueue.  When the two mix, it's a recipe
for deadlock.
> Stacktrace to follow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message