hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6860) BlockStateChange logs are too noisy
Date Thu, 28 Aug 2014 23:11:08 GMT

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

Arpit Agarwal commented on HDFS-6860:
-------------------------------------

Thanks Chang.

# In {{logAddStoredBlock}}, we can just fix the call to {{if (!blockLog.isInfoEnabled())}}
at the start of the function. Then we skip the unnecessary StringBuilder logic.
# Looks like patch needs to be rebased to current trunk.

+1 with these fixed.


> BlockStateChange logs are too noisy
> -----------------------------------
>
>                 Key: HDFS-6860
>                 URL: https://issues.apache.org/jira/browse/HDFS-6860
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.5.0
>            Reporter: Arpit Agarwal
>            Assignee: chang li
>              Labels: newbie
>         Attachments: HDFS6860.patch, HDFS6860.patch
>
>
> Block State Change logs are too noisy at the default INFO level and affect NN performance
on busy clusters.
> Most of these state changes can be logged at debug level instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message