Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 53543 invoked from network); 22 Jun 2010 03:06:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 22 Jun 2010 03:06:25 -0000 Received: (qmail 37412 invoked by uid 500); 22 Jun 2010 03:06:25 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 37322 invoked by uid 500); 22 Jun 2010 03:06:23 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 37314 invoked by uid 99); 22 Jun 2010 03:06:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jun 2010 03:06:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jun 2010 03:06:19 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o5M35vfO009811 for ; Tue, 22 Jun 2010 03:05:57 GMT Message-ID: <10841092.4321277175957229.JavaMail.jira@thor> Date: Mon, 21 Jun 2010 23:05:57 -0400 (EDT) From: "Konstantin Shvachko (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (HDFS-1222) NameNode fail stop in spite of multiple metadata directories In-Reply-To: <10387478.47731276747223521.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HDFS-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881034#action_12881034 ] Konstantin Shvachko commented on HDFS-1222: ------------------------------------------- I did not understand the failure scenario. Could you please elaborate. When the name-node gets an exception while loading image from one of the directories, does it fail or not? Is it only the startup exceptions you are testing here? > NameNode fail stop in spite of multiple metadata directories > ------------------------------------------------------------ > > Key: HDFS-1222 > URL: https://issues.apache.org/jira/browse/HDFS-1222 > Project: Hadoop HDFS > Issue Type: Bug > Components: name-node > Affects Versions: 0.20.1 > Reporter: Thanh Do > > Despite the ability to configure multiple name directories > (to store fsimage) and edits directories, the NameNode will fail stop > in most of the time it faces exception when accessing to these directories. > > NameNode fail stops if an exception happens when loading fsimage, > reading fstime, loading edits log, writing fsimage.ckpt ..., although there > are still good replicas. NameNode could have tried to work with other replicas, > and marked the faulty one. > This bug was found by our Failure Testing Service framework: > http://www.eecs.berkeley.edu/Pubs/TechRpts/2010/EECS-2010-98.html > For questions, please email us: Thanh Do (thanhdo@cs.wisc.edu) and > Haryadi Gunawi (haryadi@eecs.berkeley.edu) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.