[HDFS-10626] VolumeScanner prints incorrect IOException in reportBadBlocks operation

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Labels: supportability
• Assignee: Yiqun Lin
• Reporter: Yiqun Lin
• Created: 14/Jul/16 12:22
• Updated: 28/Aug/16 06:27
• Resolved: 28/Aug/16 06:21

Description

VolumeScanner throws incorrect IOException in datanode.reportBadBlocks. The related codes:

    public void handle(ExtendedBlock block, IOException e) {
      FsVolumeSpi volume = scanner.volume;
      ...
      try {
        scanner.datanode.reportBadBlocks(block, volume);
      } catch (IOException ie) {
        // This is bad, but not bad enough to shut down the scanner.
        LOG.warn("Cannot report bad " + block.getBlockId(), e);
      }
    }

The IOException that printed in the log should be ie rather than e which was passed in method handle(ExtendedBlock block, IOException e).
It will be a important info that can help us to know why datanode reporBadBlocks failed.

Issue Links

• duplicates: HDFS-10625 VolumeScanner to report why a block is found bad