[
https://issues.apache.org/jira/browse/HDFS-4080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493650#comment-13493650
]
Hadoop QA commented on HDFS-4080:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12552722/hdfs-4080-trunk.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3469//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3469//console
This message is automatically generated.
> 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-branch-0.23.patch,
> hdfs-4080.patch, hdfs-4080.patch, hdfs-4080-trunk.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
