[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165482#comment-16165482
]
Ajay Kumar commented on HDFS-12420:
-----------------------------------
Hi [~aw], What you said is true but as [~arpitagarwal] has pointed out current
format functionality is broken itself. It deletes the metadata while doing
nothing about the data stored in data-nodes.
We can keep the existing functionality as it is and add a new property to
identify prod cluster. By default this property will be set to non-prod. If
someone marks there cluster as prod cluster than this can be an additional
safeguard. This will maintain the backward compatibility and hopefully will
address your concerns as well.
> 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]
