Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <32340552.296311294782466382.JavaMail.jira@thor>
Date: Tue, 11 Jan 2011 16:47:46 -0500 (EST)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1505) saveNamespace appears to succeed even
 if all directories fail to save
In-Reply-To: <18540953.158441290026115210.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer commented on HDFS-1505:
----------------------------------------

> I agree saveNamespace should throw an exception if it fails all to save to any image directory. 

If that kills the namenode, then no, definitely not.  I'd much rather have the discretion to schedule the NN shutdown rather than have it just die.  Yes, there is a risk with only one image being active.  But that should be an ops call, not a dev one.

> saveNamespace appears to succeed even if all directories fail to save
> ---------------------------------------------------------------------
>
>                 Key: HDFS-1505
>                 URL: https://issues.apache.org/jira/browse/HDFS-1505
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Jakob Homan
>            Priority: Blocker
>             Fix For: 0.22.0
>
>         Attachments: hdfs-1505-test.txt
>
>
> After HDFS-1071, saveNamespace now appears to "succeed" even if all of the individual directories failed to save.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.