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

Corrupt block reporting delayed until datablock scanner thread detects it

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.5.0
    • Fix Version/s: 2.7.0
    • Component/s: None
    • Labels:
      None
    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      When there is one datanode holding the block and that block happened to be
      corrupt, namenode would keep on trying to replicate the block repeatedly but it would only report the block as corrupt only when the data block scanner thread of the datanode picks up this bad block.
      Requesting improvement in namenode reporting so that corrupt replica would be reported when there is only 1 replica and the replication of that replica keeps on failing with the checksum error.

        Attachments

        1. HDFS-7548-v5.patch
          14 kB
          Rushabh Shah
        2. HDFS-7548-v4.patch
          14 kB
          Rushabh Shah
        3. HDFS-7548-v3.patch
          12 kB
          Rushabh Shah
        4. HDFS-7548-v2.patch
          14 kB
          Rushabh Shah
        5. HDFS-7548.patch
          8 kB
          Rushabh Shah

          Issue Links

            Activity

              People

              • Assignee:
                shahrs87 Rushabh Shah
                Reporter:
                shahrs87 Rushabh Shah
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: