[
https://issues.apache.org/jira/browse/YARN-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548596#comment-13548596
]
Hadoop QA commented on YARN-325:
--------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12563946/YARN-325-branch23.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-YARN-Build/329//console
This message is automatically generated.
> 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
