Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.10.1
-
None
-
None
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.