[
https://issues.apache.org/jira/browse/HDFS-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080638#comment-13080638
]
Tsz Wo (Nicholas), SZE commented on HDFS-2229:
----------------------------------------------
In [revision
1139090|http://svn.apache.org/viewvc/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java?annotate=1139090]
(i.e. before any blockmanagement package refactoring),
- SafeModeInfo.initializeReplQueues() holds safemode lock and then acquires
namesystem write-lock in BlockManager.processMisReplicatedBlocks().
- FSNamesystem.logUpdateMasterKey(..) holds write-lock and then acquires
safemode lock in SafeModeInfo.isOn().
So the deadlock may not be related to the refactoring.
> 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
