Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 28 Oct 2012 03:51:13 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <69821884.36056.1351396273273.JavaMail.jiratomcat@arcas>
In-Reply-To: <458734953.35434.1351364472701.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HDFS-4122) Cleanup HDFS logs and reduce the
 size of logged messages
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-4122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485563#comment-13485563 ] 

Harsh J commented on HDFS-4122:
-------------------------------

Tangential, but while you are at this, can we also change the affected or surrounding log lines that go:

{code}
+ LOG.info("Exception occurred while aborting the client " + ioe);
{code}

To the more proper:

{code}
+ LOG.info("Exception occurred while aborting the client", ioe);
{code}

Such that we also don't lose stacktrace information and get the logger to print exceptions correctly?
                
> Cleanup HDFS logs and reduce the size of logged messages
> --------------------------------------------------------
>
>                 Key: HDFS-4122
>                 URL: https://issues.apache.org/jira/browse/HDFS-4122
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 2.0.0-alpha
>            Reporter: Suresh Srinivas
>            Assignee: Suresh Srinivas
>         Attachments: log.chatty.cleanup.branch1.patch, log.chatty.cleanup.trunk.patch, log.chatty.cleanup.trunk.patch
>
>
> I have attached the patch that removes unnecessary information from the log such as "Namesystem." and prefixing file information with "file" and block information with "block" etc.
> On a branch-1 log I saw it reduce the log size by ~10%.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira