Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 13 Sep 2017 17:52:00 +0000 (UTC)
From: "Vinayakumar B (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13101382.1505155311000.104298.1505325120841@Atlassian.JIRA>
In-Reply-To: <JIRA.13101382.1505155311000@Atlassian.JIRA>
References: <JIRA.13101382.1505155311000@Atlassian.JIRA> <JIRA.13101382.1505155311521@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HDFS-12420) Disable Namenode format when data
 already exists
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 13 Sep 2017 17:52:05 -0000


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

Vinayakumar B commented on HDFS-12420:
--------------------------------------

bq. Don't we already have the y/n check when data exists? Why do we need another?
Yes. We do have the prompt, which is the exact line being removed in the patch. {{fsImage.confirmFormat(force, isInteractive)}}.
User can format the existing data, if passed a -force flag or given 'y' as an answer to the prompt.

I too wanted to understand the real need for this complete disable of format.
bq. If someone really wants to delete the complete fsImage, they can first delete the metadata dir
How you can delete the shared edits dir in journal nodes manually?

I think current behavior of format works fine. -force option should not be used too lightly.

> Disable Namenode format when data already exists
> ------------------------------------------------
>
>                 Key: HDFS-12420
>                 URL: https://issues.apache.org/jira/browse/HDFS-12420
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Ajay Kumar
>            Assignee: Ajay Kumar
>         Attachments: HDFS-12420.01.patch, HDFS-12420.02.patch
>
>
> Disable NameNode format to avoid accidental formatting of Namenode in production cluster. If someone really wants to delete the complete fsImage, they can first delete the metadata dir and then run {code} hdfs namenode -format{code} manually.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org