[
https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16168303#comment-16168303
]
Ajay Kumar edited comment on HDFS-12420 at 9/15/17 6:24 PM:
------------------------------------------------------------
[~shahrs87], [~daryn],[~kihwal] Thanks for review and feedback. I have changed
property to {{"hdfs.reformat.enabled"=true}}
and moved it to DFSConfigKeys. By default property is set to true, which will
ensure existing behavior continues unless someone disables reformat.
was (Author: ajayydv):
[~shahrs87], [~daryn],[~kihwal] Thanks for review and feedback. I have changed
property to {noformat} "hdfs.reformat.enabled"=true {noformat}
and moved it to DFSConfigKeys. By default property is set to true, which will
ensure existing behavior continues unless someone disables reformat.
> 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,
> HDFS-12420.06.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]
