[ https://issues.apache.org/jira/browse/YARN-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907874#comment-13907874 ]
Vinod Kumar Vavilapalli commented on YARN-1398: ----------------------------------------------- Tx for the quick reviews, [~jianhe] and [~acmurthy]. I am checking this in now. > 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 > Assignee: Vinod Kumar Vavilapalli > 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)