Hadoop HDFS
  1. Hadoop HDFS
  2. HDFS-4212

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

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 1.2.0, 3.0.0
    • Fix Version/s: None
    • Component/s: namenode
    • Labels:
      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.

        Issue Links

          Activity

          Brandon Li created issue -
          Brandon Li made changes -
          Field Original Value New Value
          Link This issue is related to HDFS-4208 [ HDFS-4208 ]
          Yanbo Liang made changes -
          Attachment hdfs-4212-junit-test.patch [ 12555339 ]
          Brandon Li made changes -
          Assignee Brandon Li [ brandonli ]
          Tsz Wo Nicholas Sze made changes -
          Link This issue is related to HDFS-4452 [ HDFS-4452 ]
          Brandon Li made changes -
          Link This issue is duplicated by HDFS-4452 [ HDFS-4452 ]
          Brandon Li made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Duplicate [ 3 ]
          Tsz Wo Nicholas Sze made changes -
          Link This issue is related to HDFS-4452 [ HDFS-4452 ]

            People

            • Assignee:
              Brandon Li
              Reporter:
              Brandon Li
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development