hadoop-hdfs-dev mailing list archives

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

             Summary: 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
            Priority: Blocker


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