Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 34267 invoked from network); 14 Jun 2010 16:03:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Jun 2010 16:03:40 -0000 Received: (qmail 67913 invoked by uid 500); 14 Jun 2010 08:51:38 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 67759 invoked by uid 500); 14 Jun 2010 08:51:34 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 67751 invoked by uid 99); 14 Jun 2010 08:51:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jun 2010 08:51:33 +0000 X-ASF-Spam-Status: No, hits=1.8 required=10.0 tests=AWL,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gokulm@huawei.com designates 119.145.14.64 as permitted sender) Received: from [119.145.14.64] (HELO szxga01-in.huawei.com) (119.145.14.64) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jun 2010 08:51:27 +0000 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3Z00FZRXX5AS@szxga01-in.huawei.com> for common-user@hadoop.apache.org; Mon, 14 Jun 2010 16:51:06 +0800 (CST) Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3Z00AHHXX5OQ@szxga01-in.huawei.com> for common-user@hadoop.apache.org; Mon, 14 Jun 2010 16:51:05 +0800 (CST) Received: from BLRNSHTIPL6NC ([10.18.1.36]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3Z0094QXX443@szxml06-in.huawei.com> for common-user@hadoop.apache.org; Mon, 14 Jun 2010 16:51:05 +0800 (CST) Date: Mon, 14 Jun 2010 14:21:04 +0530 From: Gokulakannan M Subject: changing my hadoop log level is not getting reflected in logs To: common-user@hadoop.apache.org Reply-to: gokulm@huawei.com Message-id: Organization: htipl MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4325 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/related; boundary="Boundary_(ID_zpP8tiuqj4sTlBJ9x9Ceqg)" Thread-index: AcsLnrjeNJzPeOliQ/u1p6tihJxC0Q== --Boundary_(ID_zpP8tiuqj4sTlBJ9x9Ceqg) Content-type: multipart/alternative; boundary="Boundary_(ID_rnPSPkfAzH3psCyZ3ldprg)" --Boundary_(ID_rnPSPkfAzH3psCyZ3ldprg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, I changed the default log level of hadoop from INFO to ERROR by setting the property hadoop.root.logger to error in /conf/log4j.properties But when I start namenode, the INFO logs are seen in the log file. I did a workaround and found that HADOOP_ROOT_LOGGER is hard coded to INFO in hadoop-daemon.sh and hadoop script files in /bin. Is there anything to do with that or they are provided for any purpose?? PS: I am using hadoop 0.20.1 Thanks, Gokul **************************************************************************** *********** This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! --Boundary_(ID_rnPSPkfAzH3psCyZ3ldprg) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT

Hi,

 

            I changed the default log level of hadoop from INFO to ERROR by setting the property hadoop.root.logger to error in <hadoop>/conf/log4j.properties

 

            But when I start namenode, the INFO logs are seen in the log file. I did a workaround and found that  HADOOP_ROOT_LOGGER is hard coded to INFO in

            hadoop-daemon.sh and hadoop script files in <hadoop>/bin. Is there anything to do with that or they are provided for any purpose??

 

            PS: I am using hadoop 0.20.1

 

 Thanks,

  Gokul

 

 

 

***************************************************************************************
This e-mail and attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient's) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!

 

--Boundary_(ID_rnPSPkfAzH3psCyZ3ldprg)-- --Boundary_(ID_zpP8tiuqj4sTlBJ9x9Ceqg)--