[jira] [Updated] (HDFS-12420) Disable Namenode format when data already exists
[ https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Kumar updated HDFS-12420: -- Attachment: HDFS-12420.04.patch Fixed style-check and unit test errors. > 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, > HDFS-12420.03.patch, HDFS-12420.04.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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12420) Disable Namenode format when data already exists
[ https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Kumar updated HDFS-12420: -- Attachment: HDFS-12420.03.patch [~jnp],[~vinayrpet], thanks for suggestion about prod/non-prod. [~aw],[~anu],[~arpitagarwal] thanks for valuable feedback. I have updated the patch to include a new property to identify if cluster is marked as prod. By default property value is false and existing functionality will continue. > 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, > HDFS-12420.03.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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12420) Disable Namenode format when data already exists
[ https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Kumar updated HDFS-12420: -- Attachment: HDFS-12420.02.patch > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12420) Disable Namenode format when data already exists
[ https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Kumar updated HDFS-12420: -- Description: 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. (was: Disallow 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.) > 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 > > > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-12420) Disable Namenode format when data already exists
[ https://issues.apache.org/jira/browse/HDFS-12420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ajay Kumar updated HDFS-12420: -- Summary: Disable Namenode format when data already exists (was: Disallow Namenode format when data already exists) > 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 > > > Disallow 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org