[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165000#comment-16165000
]
Allen Wittenauer commented on HDFS-12420:
-----------------------------------------
The more I think about this, the more I'm -1:
Completely breaks automation. Automation MUST work.
bq. Let's also make the -force option a no-op. We can continue to accept it but
it should have no effect and we should print a warning saying that the force
option is being ignored.
This just makes it worse. HDFS-5138 was a disaster for automation when
-finalize was made a no-op. See HDFS-8241 for the follow-up to clean it up.
> 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]
