Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 20 Feb 2014 23:01:20 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12696412.1392937230636.77258.1392937280688@arcas>
In-Reply-To: <JIRA.12696412.1392937230636@arcas>
References: <JIRA.12696412.1392937230636@arcas>
Subject: [jira] [Created] (HDFS-5988) Bad fsimage generated after upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrew Wang created HDFS-5988:
---------------------------------

             Summary: Bad fsimage generated after upgrade
                 Key: HDFS-5988
                 URL: https://issues.apache.org/jira/browse/HDFS-5988
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.4.0
            Reporter: Andrew Wang
            Assignee: Andrew Wang
            Priority: Blocker


Internal testing revealed an issue where, after upgrading from an earlier release, we always fail to save a correct PB-based fsimage (namely, missing inodes leading to an inconsistent namespace). This results in substantial data loss, since the upgraded fsimage is broken, as well as the fsimages generated by saveNamespace and checkpointing.

This ended up being a bug in the old fsimage loading code, patch coming.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)