[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165177#comment-16165177
]
Arpit Agarwal commented on HDFS-12420:
--------------------------------------
Allen, thanks for bringing up the automation concern. We certainly don't want
to break any deployment scripts. This patch will not break scripted deployment
of new clusters since it eliminates the prompt completely.
Formatting clusters with pre-existing data was a bad idea in the first place.
It deletes the NameNode metadata and leaves the cluster in an unusable state
since DataNodes cannot connect anymore. I don't think any existing automation
can depend on this behavior since it is functionally broken.
> 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]
