[
https://issues.apache.org/jira/browse/HADOOP-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662194#action_12662194
]
Brian Bockelman commented on HADOOP-4995:
-----------------------------------------
Re: Konstantin: I still consider the secondary name-node part of the "online
system".
I want to be able to take a completely offline image - perhaps something we
pulled off the tape - and make sure that it's at least valid enough that a
namenode could load it into memory. It'd be a way that we can do a "light
audit" of our backup copies.
Currently, the best we can do is "try and pray" (and it's a manual process).
> Offline Namenode fsImage verification
> -------------------------------------
>
> Key: HADOOP-4995
> URL: https://issues.apache.org/jira/browse/HADOOP-4995
> Project: Hadoop Core
> Issue Type: New Feature
> Reporter: Brian Bockelman
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
