hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3803) BlockPoolSliceScanner new work period notice is very chatty at INFO level
Date Wed, 15 Aug 2012 01:40:38 GMT

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

Suresh Srinivas commented on HDFS-3803:

bq. I disagree, without the "Starting a new period" message it's very difficult to diagnose
the block pool scanner in production scenarios.
Let me know what production scenario you have in mind. Debug logs should be the last resort
for this kind of debugging. For thread related issues one can look at java stack. I agree
we should do it with metrics.

Currently this log is an annoyance. When HDFS-3194 goes in we can undo this change. 
> BlockPoolSliceScanner new work period notice is very chatty at INFO level
> -------------------------------------------------------------------------
>                 Key: HDFS-3803
>                 URL: https://issues.apache.org/jira/browse/HDFS-3803
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: data-node
>    Affects Versions: 2.1.0-alpha, 2.0.1-alpha
>         Environment: Hadoop 2.0.1-alpha-SNAPSHOT
>            Reporter: Andrew Purtell
>            Priority: Minor
>             Fix For: 2.1.0-alpha, 3.0.0
>         Attachments: HDFS-3803.patch
> One line of ~140 chars logged every 5 seconds. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message