Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-1297

datanode sending block reports to namenode once every second

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.13.0
    • Component/s: None
    • Labels:
      None

      Description

      The namenode is requesting a block to be deleted. The datanode tries this operation and encounters an error because the block is not in the blockMap. The processCommand() method raises an exception. The code is such that the variable lastBlockReport is not set if processCommand() raises an exception. This means that the datanode immediately send another block report to the namenode. The eats up quite a bit of CPU on namenode.

      In short, the above condition causes the datanode to send blockReports almost once every second!

      I propose that we do the following:

      1. in Datanode.offerService, replace the following piece of code

      DatanodeCommand cmd = namenode.blockReport(dnRegistration,
      data.getBlockReport());
      processCommand(cmd);
      lastBlockReport = now;

      with

      DatanodeCommand cmd = namenode.blockReport(dnRegistration,
      data.getBlockReport());
      lastBlockReport = now;
      processCommand(cmd);

      2. In FSDataSet.invalidate:
      a) continue to process all blocks in invalidBlks[] even if one in the middle encounters a problem.
      b) if getFile() returns null, still invoke volumeMap.get() and print whether we found the block in
      volumes or not. The volumeMap is used to generate the blockReport and this might help in debugging.
      [

        Attachments

        1. datanodeDeleteBlocks2.patch
          4 kB
          dhruba borthakur
        2. datanodeDeleteBlocks-0.12.3.patch
          4 kB
          dhruba borthakur

          Issue Links

            Activity

              People

              • Assignee:
                dhruba dhruba borthakur
                Reporter:
                dhruba dhruba borthakur
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: