hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-7503) Namenode restart after large deletions can cause slow processReport (due to logging)
Date Tue, 09 Dec 2014 23:05:12 GMT
Arpit Agarwal created HDFS-7503:
-----------------------------------

             Summary: Namenode restart after large deletions can cause slow processReport
(due to logging)
                 Key: HDFS-7503
                 URL: https://issues.apache.org/jira/browse/HDFS-7503
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: namenode
    Affects Versions: 2.6.0, 1.2.1
            Reporter: Arpit Agarwal
            Assignee: Arpit Agarwal


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:
{code}
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.
{code}
This log is printed within FSNamsystem lock. This can cause namenode to take long time in
coming out of safemode.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message