hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1139) All block trasitions should be logged at log level INFO
Date Thu, 03 May 2007 20:55:15 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493520
] 

Michael Bieniosek commented on HADOOP-1139:
-------------------------------------------

I don't have a problem losing blocks on my HDFS installation (possibly because I have a much
smaller installation).  I don't see why I should pay the price of having my namenode log flooded
with these messages.  If you need to debug block related errors, why don't you just set the
namenode logging to DEBUG on your installation?

> All block trasitions should be logged at log level INFO
> -------------------------------------------------------
>
>                 Key: HADOOP-1139
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1139
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>
> The namenode records block trasitions in its log file. It is seen that some of the block
transition messages were being logged at debug level. These should be done at INFO level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message