hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2229) Deadlock in NameNode
Date Thu, 11 Aug 2011 22:34:27 GMT

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

Hudson commented on HDFS-2229:
------------------------------

Integrated in Hadoop-Common-trunk-Commit #731 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/731/])
    HDFS-2229. Fix a deadlock in namenode by enforcing lock acquisition ordering.

szetszwo : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1156847
Files : 
* /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* /hadoop/common/trunk/hdfs/CHANGES.txt
* /hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java


> Deadlock in NameNode
> --------------------
>
>                 Key: HDFS-2229
>                 URL: https://issues.apache.org/jira/browse/HDFS-2229
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Tsz Wo (Nicholas), SZE
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: cycle1.png, cycle2.png, h2229_20110807.patch, h2229_20110810.patch
>
>
> Either I am doing something incredibly stupid, or something about my environment is completely
weird, or may be it really is a valid bug. I am running a NameNode deadlock consistently with
0.23 HDFS. I could never start NN successfully.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message