hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12420) Disable Namenode format when data already exists
Date Wed, 13 Sep 2017 16:23:00 GMT

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

Anu Engineer commented on HDFS-12420:
-------------------------------------

[~aw] This does break backward compatibility. So wanted to hear your thought on this. 
The reason why we are doing this is that people are capable of formatting clusters with data
on them :). Just wondering how big of an issue would this be if we put this in 3.0?. Appreciate
any comments you might have.


> 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


Mime
View raw message