You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/07/07 14:38:36 UTC

[jira] [Commented] (MAPREDUCE-4372) Deadlock in Resource Manager between SchedulerEventDispatcher.EventProcessor and Shutdown hook manager

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408653#comment-13408653 ] 

Hudson commented on MAPREDUCE-4372:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #306 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/306/])
    svn merge -c 1354531 FIXES: MAPREDUCE-4372. Deadlock in Resource Manager (Devaraj K via bobby) (Revision 1358402)

     Result = UNSTABLE
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1358402
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/ResourceManager.java

                
> Deadlock in Resource Manager between SchedulerEventDispatcher.EventProcessor and Shutdown hook manager
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-4372
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4372
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, resourcemanager
>    Affects Versions: 2.0.0-alpha, 3.0.0
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>             Fix For: 0.23.3, 2.0.1-alpha, 3.0.0
>
>         Attachments: MAPREDUCE-4372-1.patch, MAPREDUCE-4372.patch, rm-threaddump.out
>
>
> Please find the attached resource manager thread dump for the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira