[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168194#comment-16168194
]
Kihwal Lee commented on HDFS-12420:
-----------------------------------
Adding an extra layer of protection from mistakes is fine, but we can't assume
that prod implies no reformat ever. Don't force people to reclassify their
cluster for a command.
bq. If there's a conf, "hadoop.is.prod.cluster" is silly. Call it something
more like "hdfs.reformat.enabled".
Something like this will be better. Also, the default behavior should be
backward compatible.
> Disable Namenode format for prod clusters 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,
> HDFS-12420.03.patch, HDFS-12420.04.patch, HDFS-12420.05.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]
