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 "Vinay (JIRA)" <ji...@apache.org> on 2013/09/05 10:23:52 UTC

[jira] [Resolved] (HDFS-3736) Failure in starting NN due to fsimage loading failure

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

Vinay resolved HDFS-3736.
-------------------------

    Resolution: Duplicate

HDFS-4596 fixes the current issue and its already committed. So resolving this issue as duplicate.
                
> Failure in starting NN due to fsimage loading failure
> -----------------------------------------------------
>
>                 Key: HDFS-3736
>                 URL: https://issues.apache.org/jira/browse/HDFS-3736
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: ha, namenode
>    Affects Versions: 2.0.0-alpha
>            Reporter: suja s
>            Assignee: Andrew Wang
>
> Came across a situation as follows in our test environment.
> NNs running in HA mode.
> While uploading checkpoint, MD5 file renaming from tmp to actual file failed due to some reason which is unknown (non IO exception).
> At the same time at standby side, connection imeout occured.
> This lead to tmp MD5 file and original fsimage file (ckpt fsimage file was renamed successfully to original fsimage file) in the name dir of active NN.
> On NN restart it checks for MD5 file and since it is not found, startup is failing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira