hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4080) Add an option to disable block-level state change logging
Date Fri, 19 Oct 2012 17:14:12 GMT

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

Aaron T. Myers commented on HDFS-4080:
--------------------------------------

Would it be possible to just move the logging outside of the FSNS lock? Jing did a similar
change recently in HDFS-4052.
                
> 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
>
> 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

Mime
View raw message