You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2007/06/01 00:54:15 UTC

[jira] Updated: (HADOOP-1139) All block trasitions should be logged at log level INFO

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

dhruba borthakur updated HADOOP-1139:
-------------------------------------

    Attachment: blockTransitionLog2.patch

This new patch incorporates a few of Hairong's comments.

1. There is no need to check LOG/isInfoEnabled() because logs are typically at INFO level anyway.
2. Change the comment in addStoredBlock() on why we log when safemode is off.

> 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
>         Attachments: blockTransitionLog2.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.