[
https://issues.apache.org/jira/browse/HDFS-9839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155732#comment-15155732
]
ASF GitHub Bot commented on HDFS-9839:
--------------------------------------
GitHub user arp7 opened a pull request:
https://github.com/apache/hadoop/pull/78
HDFS-9839. Reduce verbosity of processReport logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arp7/hadoop HDFS-9839
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hadoop/pull/78.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #78
----
commit 8b23b41ada23168fe2cb71f4a3b920c68e66ee74
Author: Arpit Agarwal <[email protected]>
Date: 2016-02-20T18:43:14Z
HDFS-9839. Reduce verbosity of processReport logging
----
> 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
>
> {{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)
