[
https://issues.apache.org/jira/browse/HDFS-5988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908168#comment-13908168
]
Hudson commented on HDFS-5988:
------------------------------
FAILURE: Integrated in Hadoop-Yarn-trunk #488 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/488/])
HDFS-5988. Bad fsimage always generated after upgrade. (wang) (wang:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1570429)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImageFormat.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineImageViewer/LsrPBImage.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestDFSUpgradeFromImage.java
> 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)
