[
https://issues.apache.org/jira/browse/HDFS-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493250#comment-13493250
]
Kihwal Lee commented on HDFS-4080:
----------------------------------
bq. instead of the logger name org.apache.hadoop.hdfs.StateChange.block, which
is a change from the existing name, should be just change it to
BlockStateChange. This potentially saves a logging from printing the entire
package name?
I think keeping the hierarchical naming is better. To reduce the amount of log
data, the layout can include something like %c{2} or omit "c" entirely since
these lines already have a distinct signature. Do you think it is better to add
the logger config with this layout change to
hadoop-common-project/hadoop-common/src/main/conf/log4j.properties? If so, as a
part of this jira or a separate common one?
> Add an option to disable block-level state change logging
> ---------------------------------------------------------
>
> Key: HDFS-4080
> URL: https://issues.apache.org/jira/browse/HDFS-4080
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 3.0.0, 2.0.3-alpha
> Reporter: Kihwal Lee
> Assignee: Kihwal Lee
> Attachments: hdfs-4080.1.patch, hdfs-4080.patch, hdfs-4080.patch
>
>
> Although the block-level logging in namenode is useful for debugging, it can
> add a significant overhead to busy hdfs clusters since they are done while
> the namespace write lock is held. One example is shown in HDFS-4075. In this
> example, the write lock was held for 5 minutes while logging 11 million log
> messages for 5.5 million block invalidation events.
> It will be useful if we have an option to disable these block-level log
> messages and keep other state change messages going. If others feel that
> they can turned into DEBUG (with addition of isDebugEnabled() checks), that
> may also work too, but there might be people depending on the messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
