Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C56EC6CD for ; Sun, 14 Jul 2013 06:36:05 +0000 (UTC) Received: (qmail 10773 invoked by uid 500); 14 Jul 2013 06:35:56 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 10209 invoked by uid 500); 14 Jul 2013 06:35:49 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 10202 invoked by uid 99); 14 Jul 2013 06:35:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jul 2013 06:35:47 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [49.212.34.109] (HELO oss.nttdata.co.jp) (49.212.34.109) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 14 Jul 2013 06:35:41 +0000 Received: from [192.168.0.29] (unknown [70.1.69.168]) by oss.nttdata.co.jp (Postfix) with ESMTP id 6192D17EE01 for ; Sun, 14 Jul 2013 15:35:18 +0900 (JST) Message-ID: <51E24694.6020104@oss.nttdata.co.jp> Date: Sat, 13 Jul 2013 23:35:00 -0700 From: Shinichi Yamashita User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: user@hadoop.apache.org Subject: Re: How to control of the output of "/stacks" References: <51E07B17.8090806@oss.nttdata.co.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.7 at oss.nttdata.co.jp X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on oss.nttdata.co.jp X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-99.0 required=13.0 tests=CONTENT_TYPE_PRESENT, ONLY1HOPDIRECT,RDNS_NONE,USER_IN_WHITELIST autolearn=no version=3.2.5 Thank you for comment. I understand that stacks is very useful for debug and trouble-shooting. I think that the change of LogLevel has a big influence on others. So the control of the output to log file of stack traces is necessary. I'll register patch with JIRA. Regards, Shinichi Yamashita (2013/07/12 19:24), Harsh J wrote: > The logging has sometimes come useful in debugging (i.e. if the stack > on the UI went uncaptured, the log helps). It is currently not > specifically toggle-able. I suppose it is OK to set it as DEBUG > though. Can you file a JIRA for that please? > > The only way you can disable it right now is by (brute-forcibly) > adding the below to the daemon's log4j.properties: > > log4j.logger.org.apache.hadoop.http.HttpServer=WARN > > Which may not be so ideal as we may miss other INFO from HttpServer generically. > > On Sat, Jul 13, 2013 at 3:24 AM, Shinichi Yamashita > wrote: >> Hi, >> >> I can see the stack trace of the node when I access "/stacks" of Web UI. >> And stack trace is output in the log file of the node, too. >> Because the expansion of the log file and hard to see it, I don't want >> to output it in a log file. >> Is there the method to solve this problem? >> >> Regards, >> Shinichi Yamashita > > >