hadoop-hdfs-issues mailing list archives

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

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

Suresh Srinivas commented on HDFS-2229:

This is related to block manager refactored out of FSNamesystem. Nicholas, could you please
take a look at this?

Namenode main thread grabs safemode lock and BlockManager#processMisReplicatedBlocks() takes
namenode writelock
AbstractDelegationTokenSecretManager grabs namenode writelock and then tris to grab safemode

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

> 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


View raw message