Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 11 Aug 2011 00:01:28 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <634763487.25966.1313020888246.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <743868807.11254.1312543167473.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2229) Deadlock in NameNode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Todd Lipcon commented on HDFS-2229:
-----------------------------------

Hi Nicholas. I'm not sure this fixes the issue - if you look at the stack trace, initializeReplQueues() is being called by leave() which is also synchronized on SafeModeInfo. 

> 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