hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2229) Deadlock in NameNode
Date Sun, 07 Aug 2011 20:36:27 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-2229:
----------------------------------------------

> The order in all the refactoring needs to be ensured to grab namenode lock before grabbing
safemode lock.

Hi Suresh, the goal of refactoring was to move the code out from FSNamesystem.  All changes
were straightforward and all lock orders were preserved (and so I refused to fix locking problem
in the refactoring previously.)  Unfortunately, we did see some locking problem.

> Deadlock in NameNode
> --------------------
>
>                 Key: HDFS-2229
>                 URL: https://issues.apache.org/jira/browse/HDFS-2229
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 0.23.0
>            Reporter: Vinod Kumar Vavilapalli
>
> 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