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

NameNode can't differentiate between a never-created block and a block which is really missing

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 1.2.0, 3.0.0-alpha1
    • None
    • namenode
    • None

    Description

      In one test case, NameNode allocated a block and then was killed before the client got the addBlock response.

      After NameNode restarted, the block which was never created was considered as a missing block and FSCK would report the file is corrupted.

      The problem seems to be that, NameNode can't differentiate between a never-created block and a block which is really missing.

      Attachments

        1. hdfs-4212-junit-test.patch
          3 kB
          Yanbo Liang

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. HDFS-4452 getAdditionalBlock() can create multiple blocks if the client times out and retries.

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. HDFS-4208 NameNode could be stuck in SafeMode due to never-created blocks

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              brandonli Brandon Li
              brandonli Brandon Li
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: