[
https://issues.apache.org/jira/browse/HADOOP-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493515
]
Sameer Paranjpye commented on HADOOP-1139:
------------------------------------------
> What's the motivation to log these at INFO? Is there any reason I would care
> about block transition messages if I were not debugging hadoop?
Block related errors (blocks getting lost, having too many or too few replicas
etc.) are very hard to diagnose without a history of block events. These bugs
are frequently exposed by running systems and the circumstances in which they
occur can be hard to reproduce in a testbed. If you lost a block on your HDFS
installation, you would want to know why, that answer can be obtained with much
less pain if there is a trail to follow.
> 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.
