Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-7788

Post-2.6 namenode may not start up with an image containing inodes created with an old release.

    XMLWordPrintableJSON

Details

    • Reviewed

    Description

      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.

      Attachments

        1. HDFS-7788-binary.patch
          7 kB
          Rushabh Shah
        2. rushabh.patch
          7 kB
          Kihwal Lee
        3. HDFS-7788-2.6.0.patch
          6 kB
          Sangjin Lee
        4. image-with-zero-block-size.tar.gz
          1 kB
          Sangjin Lee

        Activity

          People

            shahrs87 Rushabh Shah
            kihwal Kihwal Lee
            Votes:
            0 Vote for this issue
            Watchers:
            16 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: