[
https://issues.apache.org/jira/browse/HADOOP-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493253
]
dhruba borthakur commented on HADOOP-1139:
------------------------------------------
I think the namenode will be filled with block transition messages if we log
all of them at INFO level. The following are block transition events:
1. Allocate a block for a file that is being written to. Log this event.
2. When the datanodes confirm receipt of a block, log this event.
3. When the file is closed, these blocks move to a different category. Log this
event.
4. When a file gets deleted, the namenode tells the datanode to delete those
block. Log these.
5. When a datanode dies, replicate blocks. Log these events.
I am guessing that Items 1, 2 and 3 will flood the namenode log.
> 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.
