Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1735533556.1240962390695.JavaMail.jira@brutus>
Date: Tue, 28 Apr 2009 16:46:30 -0700 (PDT)
From: "Hairong Kuang (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5711) Change Namenode file close log to
 info
In-Reply-To: <1323313666.1240336007663.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-5711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703883#action_12703883 ] 

Hairong Kuang commented on HADOOP-5711:
---------------------------------------

Maybe a more informative message is better, something like "file xx is closed by yy".

> Change Namenode file close log to info
> --------------------------------------
>
>                 Key: HADOOP-5711
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5711
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Tsz Wo (Nicholas), SZE
>            Priority: Minor
>         Attachments: 5711_20090422.patch
>
>
> It is hard to tell whether a file is closed or not from the Namenode log if the stateChangeLog is not set to debug level.  It is better to log file close in info level. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.