[
https://issues.apache.org/jira/browse/HDFS-16649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ujjawal Kumar updated HDFS-16649:
---------------------------------
Description: In our production system, we have observed that if a namenode
hosting machine is down for some time, starting the namenode again fails due to
an error of missing edit logs. This always requires doing a manual bootstrap
(using command {{namenode -bootstrapStandby -nonInteractive -force}} ). We
should make this atleast configurable so that a namenode startup can
automatically bootstrap if the issue is due to missing edit logs.
!namenode_startup_error.png! (was: In our production system, we have observed
that if a namenode hosting machine is down for some time, starting the namenode
again fails due to an error of missing edit logs. This always requires doing a
manual bootstrap (using command {{namenode -bootstrapStandby -nonInteractive
-force}} ). We should make this configurable so that a namenode startup can
automatically bootstrap if the issue is due to missing edit logs.
!namenode_startup_error.png!)
> Allow an option to automatically bootstrap standby namenode during startup
> --------------------------------------------------------------------------
>
> Key: HDFS-16649
> URL: https://issues.apache.org/jira/browse/HDFS-16649
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.10.1
> Reporter: Ujjawal Kumar
> Priority: Minor
> Attachments: namenode_startup_error.png
>
>
> In our production system, we have observed that if a namenode hosting machine
> is down for some time, starting the namenode again fails due to an error of
> missing edit logs. This always requires doing a manual bootstrap (using
> command {{namenode -bootstrapStandby -nonInteractive -force}} ). We should
> make this atleast configurable so that a namenode startup can automatically
> bootstrap if the issue is due to missing edit logs.
> !namenode_startup_error.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
