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

DFSClient.getBlockLocations returns BlockLocations with no indication that the corresponding blocks are corrupt

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.22.0
    • hdfs-client
    • None
    • Reviewed

    Description

      When there are no uncorrupted replicas of a block, FSNamesystem.getBlockLocations returns LocatedBlocks corresponding to corrupt blocks. When DFSClient converts these to BlockLocations, the information that the corresponding block is corrupt is lost. We should add a field to BlockLocation to indicate whether the corresponding block is corrupt in order to warn the client that reading this block will fail. This would be especially useful for tools such as RAID FSCK, which could then easily inspect whether data or parity blocks are corrupted without having to make direct RPC calls.

      Attachments

        1. HDFS-1483.2.patch
          3 kB
          Patrick Kling
        2. HDFS-1483.patch
          4 kB
          Patrick Kling

        Issue Links

          Activity

            People

              pkling Patrick Kling
              pkling Patrick Kling
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: