You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2014/03/11 01:25:48 UTC

[jira] [Commented] (HDFS-6085) Improve CacheReplicationMonitor log messages a bit

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

Andrew Wang commented on HDFS-6085:
-----------------------------------

This looks good. Do you want to try lowering the log level for CacheManager#cacheRepors in this patch as well? Right now it's pretty spammy at INFO, and I imagine it being even worse on a large cluster.

Otherwise, +1 pending.

> Improve CacheReplicationMonitor log messages a bit
> --------------------------------------------------
>
>                 Key: HDFS-6085
>                 URL: https://issues.apache.org/jira/browse/HDFS-6085
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: 2.4.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-6085.001.patch
>
>
> It would be nice if the CacheReplicationMonitor logs would print out information about blocks when at TRACE level.  We also could be a bit more organized about logs and include the directive ID in the log, so that it was clear what each log message referred to.



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