You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2019/11/12 18:15:00 UTC
[jira] [Resolved] (HDFS-14981) BlockStateChange logging is
exceedingly verbose
[ https://issues.apache.org/jira/browse/HDFS-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk resolved HDFS-14981.
---------------------------------
Resolution: Duplicate
Yep, I think you're right. Thanks for the pointer [~weichiu].
> BlockStateChange logging is exceedingly verbose
> -----------------------------------------------
>
> Key: HDFS-14981
> URL: https://issues.apache.org/jira/browse/HDFS-14981
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: logging
> Reporter: Nick Dimiduk
> Priority: Major
>
> On a moderately loaded cluster, name node logs are flooded with entries of {{INFO BlockStateChange...}}, to the tune of ~30 lines per millisecond. This provides operators with little to no usable information. I suggest reducing this log message to {{DEBUG}}. Perhaps this information (and other logging related to it) should be directed to a dedicated block-audit.log file that can be queried, rotated on a separate schedule from the log of the main process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org