Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 26 Feb 2013 00:50:18 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12600652.1343653119159.338056.1361839818195@arcas>
In-Reply-To: <JIRA.12600652.1343653119159@arcas>
References: <JIRA.12600652.1343653119159@arcas>
Subject: [jira] [Assigned] (HDFS-3736) Failure in starting NN due to fsimage
 loading failure
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Wang reassigned HDFS-3736:
---------------------------------

    Assignee: Andrew Wang
    
> 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