[ https://issues.apache.org/jira/browse/YARN-1398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908397#comment-13908397 ]
Hudson commented on YARN-1398: ------------------------------ SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1705 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1705/]) YARN-1398. Fixed a deadlock in ResourceManager between users requesting queue-acls and completing containers. Contributed by Vinod Kumar Vavilapalli. (vinodkv: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570415) * /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt * /hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/LeafQueue.java > 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 > Fix For: 2.4.0 > > 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)