[
https://issues.apache.org/jira/browse/HADOOP-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1139:
---------------------------------
Resolution: Fixed
Fix Version/s: 0.14.0
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Dhruba!
Michael: the idea of this change is that, if you ever do lose a block, you'll
wish you had these events logged. I think it has been constrained so that the
log is not flooded, but important events are still logged to permit some
post-mortem analysis.
> 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
> Fix For: 0.14.0
>
> Attachments: blockTransitionLog3.patch
>
>
> 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.
