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

Namenode restart after large deletions can cause slow processReport (due to logging)

    Details

    • Target Version/s:
    • Hadoop Flags:
      Reviewed

      Description

      If a large directory is deleted and namenode is immediately restarted, there are a lot of blocks that do not belong to any file. This results in a log:

      2014-11-08 03:11:45,584 INFO BlockStateChange (BlockManager.java:processReport(1901)) - BLOCK* processReport: blk_1074250282_509532 on 172.31.44.17:1019 size 6 does not belong to any file.
      

      This log is printed within FSNamsystem lock. This can cause namenode to take long time in coming out of safemode.

      One solution is to downgrade the logging level.

        Attachments

        1. HDFS-7503.trunk.02.patch
          3 kB
          Arpit Agarwal
        2. HDFS-7503.trunk.01.patch
          0.9 kB
          Arpit Agarwal
        3. HDFS-7503.branch-1.patch
          0.8 kB
          Arpit Agarwal
        4. HDFS-7503.branch-1.02.patch
          3 kB
          Arpit Agarwal

          Issue Links

            Activity

              People

              • Assignee:
                arpitagarwal Arpit Agarwal
                Reporter:
                arpitagarwal Arpit Agarwal
              • Votes:
                0 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: