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


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

Andrew Wang updated HDFS-5988:
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.0
           Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2, branch-2.4. Thanks for the quick +1 Jing!

> Bad fsimage always 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
>             Fix For: 2.4.0
>
>         Attachments: hdfs-5988-1.patch
>
>
> 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)