You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by ts...@yahoo.gr.INVALID on 2017/02/15 07:56:01 UTC

Problem on ThriftAccessLogger logs on localhost mode #storm 1.0.2

There is a problem an you cannot set the logging level on localhost mode ehen using DRPC. It constantly sends logging messages such as "access from:  principal:  operation: fetchRequest" that cannot be deactivated, making debugging impossible...

Re: Problem on ThriftAccessLogger logs on localhost mode #storm 1.0.2

Posted by Bobby Evans <ev...@yahoo-inc.com.INVALID>.

All of the logging is through slf4j.  We include on the classpath the right plugins to have slf4j backed by log4j2.  So you can configure log4j2 and all of the logging should follow it.  For the storm jar command we do not explicitly set any config for log4j2 is using the default, printing to stdout.  You can override command line opts for storm jar by setting the environment variable STORM_JAR_JVM_OPTS.  If you are running unit tests you can override it with the command line options of however you launch your tests.  If by localhost mode you mean running storm drpc just locally you can edit log4j/cluster.xml.
That is the access logger that is writing those out.


- Bobby

On Wednesday, February 15, 2017, 1:56:31 AM CST, tsantalos-spamia@yahoo.gr.INVALID <ts...@yahoo.gr.INVALID> wrote:There is a problem an you cannot set the logging level on localhost mode ehen using DRPC. It constantly sends logging messages such as "access from:  principal:  operation: fetchRequest" that cannot be deactivated, making debugging impossible...