Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 13 Sep 2011 21:33:09 +0000 (UTC)
From: "Eric Yang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <385808715.24192.1315949589265.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <978071940.23784.1315945268933.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HADOOP-7633) log4j.properties should be added to
 the hadoop conf on deploy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Yang updated HADOOP-7633:
------------------------------

    Attachment: HADOOP-7633-trunk.patch

Same patch for trunk.

> log4j.properties should be added to the hadoop conf on deploy
> -------------------------------------------------------------
>
>                 Key: HADOOP-7633
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7633
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>            Reporter: Arpit Gupta
>            Assignee: Eric Yang
>             Fix For: 0.20.205.0
>
>         Attachments: HADOOP-7633-trunk.patch, HADOOP-7633.patch
>
>
> currently the log4j properties are not present in the hadoop conf dir. We should add them so that log rotation happens appropriately and also define other logs that hadoop can generate for example the audit and the auth logs as well as the mapred summary logs etc.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira