hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaoyu Yao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9839) Reduce verbosity of processReport logging
Date Sun, 21 Feb 2016 02:26:18 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155858#comment-15155858
] 

Xiaoyu Yao commented on HDFS-9839:
----------------------------------

Patch LGTM. +1.

> Reduce verbosity of processReport logging
> -----------------------------------------
>
>                 Key: HDFS-9839
>                 URL: https://issues.apache.org/jira/browse/HDFS-9839
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.8.0
>            Reporter: Arpit Agarwal
>            Assignee: Arpit Agarwal
>         Attachments: HDFS-9839.01.patch
>
>
> {{BlockManager#processReport}} logs one line for each invalidated block at INFO. HDFS-7503
moved this logging outside the NameSystem write lock but we still see the NameNode being slowed
down when the number of block invalidations is very large e.g. just after a large amount of
data is deleted.
> {code}
>       for (Block b : invalidatedBlocks) {
>         blockLog.info("BLOCK* processReport: {} on node {} size {} does not " +
>             "belong to any file", b, node, b.getNumBytes());
>       }
> {code}
> We can change this statement to DEBUG and just log the number of block invalidations
at INFO.



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

Mime
View raw message