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 Mon, 08 Aug 2011 23:00:28 GMT

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

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

Hi Todd, the detected deadlocks seem false alerts since setBlockTotal() is only invoked in
activate(..) before starting the lease monitor thread.

BTW, are you running it against trunk?  The line numbers are off.

> 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
>            Priority: Blocker
>         Attachments: cycle1.png, cycle2.png, h2229_20110807.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