Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <9070403.1180742955879.JavaMail.jira@brutus>
Date: Fri, 1 Jun 2007 17:09:15 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1139) All block trasitions should be
 logged at log level INFO
In-Reply-To: <3452677.1174517192203.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hairong Kuang commented on HADOOP-1139:
---------------------------------------

+1 Code looks good.

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