hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7788) Post-2.6 namenode may not start up with an image containing inodes created with an old release.
Date Sat, 21 Feb 2015 12:18:16 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14330177#comment-14330177
] 

Hudson commented on HDFS-7788:
------------------------------

SUCCESS: Integrated in Hadoop-Yarn-trunk #845 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/845/])
HDFS-7788. Post-2.6 namenode may not start up with an image containing inodes created with
an old release. Contributed by Rushabh Shah. (kihwal: rev 7ae5255a1613ccfb43646f33eabacf1062c86e93)
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/INodeFile.java
* hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/util/LongBitFormat.java
* hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestFSImage.java
* hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* hadoop-hdfs-project/hadoop-hdfs/src/test/resources/image-with-zero-block-size.tar.gz


> Post-2.6 namenode may not start up with an image containing inodes created with an old
release.
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-7788
>                 URL: https://issues.apache.org/jira/browse/HDFS-7788
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Rushabh S Shah
>            Priority: Blocker
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7788-binary.patch, rushabh.patch
>
>
> Before HDFS-4305, which was fixed in 2.1.0-beta, clients could specify arbitrarily small
preferred block size for a file including 0. This was normally done by faulty clients or failed
creates, but it was possible.
> Until 2.5, reading a fsimage containing inodes with 0 byte preferred block size was allowed.
So if a fsimage contained such an inode, the namenode would come up fine.  In 2.6, the preferred
block size is required be > 0. Because of this change, the image that worked with 2.5 may
not work with 2.6.
> If a cluster ran a version of hadoop earlier than 2.1.0-beta before, it is under this
risk even if it worked fine with 2.5.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message