Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
Currently, there is no way to verify that a copy of the fsImage is not corrupt. I propose that we should have an offline tool that loads the fsImage into memory to see if it is usable. This will allow us to automate backup testing to some extent.
One can start a namenode process on the fsImage to see if it can be loaded, but this is not easy to automate.
To use HDFS in production, it is greatly desired to have both checkpoints - and have some idea that the checkpoints are valid! No one wants to see the day where they reload from backup only to find that the fsImage in the backup wasn't usable.