[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165484#comment-16165484
]
Anu Engineer commented on HDFS-12420:
-------------------------------------
[~aw] Thanks for your comments.
bq. The argument here is the same as "newfs should fail if it detects a
partition table. You'll need to dd onto the raw disk to wipe it out first". If
you ask any experienced admin, 9/10 they're going to tell you that makes zero
sense.
Makes sense, Let us not proceed down this path. The only difference is that in
case of Hadoop the damage that a command can do is multiplied by the number of
data nodes.
Having seen that accidental formats can happen, may be being able to tag a
cluster as "production" like discussed above is a better idea?
> 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: [email protected]
For additional commands, e-mail: [email protected]
