You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/21 19:56:40 UTC

[jira] [Resolved] (HDFS-215) Offline Namenode fsImage verification

     [ https://issues.apache.org/jira/browse/HDFS-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HDFS-215.
-----------------------------------

    Resolution: Fixed

As Jakob points out, oiv does this. Closing as fixed.

> Offline Namenode fsImage verification
> -------------------------------------
>
>                 Key: HDFS-215
>                 URL: https://issues.apache.org/jira/browse/HDFS-215
>             Project: Hadoop HDFS
>          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 was sent by Atlassian JIRA
(v6.2#6252)