Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <16582352.105641291428851429.JavaMail.jira@thor>
Date: Fri, 3 Dec 2010 21:14:11 -0500 (EST)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Commented: (HDFS-1508) Ability to do savenamespace without
 being in safemode
In-Reply-To: <8808900.184241290122113827.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-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966779#action_12966779 ] 

Todd Lipcon commented on HDFS-1508:
-----------------------------------

I'm not arguing one way or the other, but I'm curious whether an alternative solution would be to have the 2NN factor in the number of failed name.dirs when deciding to run a checkpoint. Right now we have a config to force a checkpoint after a certain size of edits - why not also have the 2NN check for failed but restorable dirs and force a checkpoint in that case too?

> Ability to do savenamespace without being in safemode
> -----------------------------------------------------
>
>                 Key: HDFS-1508
>                 URL: https://issues.apache.org/jira/browse/HDFS-1508
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: savenamespaceWithoutSafemode.txt, savenamespaceWithoutSafemode2.txt, savenamespaceWithoutSafemode3.txt
>
>
> In the current code, the administrator can run savenamespace only after putting the namenode in safemode. This means that applications that are writing to HDFS encounters errors because the NN is in safemode. We would like to allow saveNamespace even when the namenode is not in safemode.
> The savenamespace command already acquires the FSNamesystem writelock. There is no need to require that the namenode is in safemode too.

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