Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Hadoop >> mail # user >> Re: How to control of the output of "/stacks"


Copy link to this message
-
Re: How to control of the output of "/stacks"
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
<[EMAIL PROTECTED]> 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

--
Harsh J
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB