There are specific requirements with where logs should be placed so we
explicitly didn't make it simple for users to override the logging configs
unless you own the cluster. If you are still using logback you should look
into upgrading to 0.10.X at least and preferably to a 1.x release. In those
versions there are APIs to be able to set the logging levels dynamically as
your topology is running (turn on debug logging for the next 10 mins). We
wanted to control log levels as well because logging too much has a very
significant impact on a running topology (300x less throughput in extreme
cases) and it is not obvious to a lot of users why it is slow.
If you really want to change the configuration you can do it programatically,
you might also be able to mess with the System properties on the command line
for your worker to override the one the supervisor sets when launching your
workers.
- Bobby
On Wednesday, September 7, 2016 7:06 AM, dev opts <[email protected]>
wrote:
Hi all,
I got some questions here for the storm log configuration.
There is a topology built by maven and a logback.xml in the
/src/main/resources path.
when i ran the topology on the local cluster,the log message about the topology
was wrote
a my file which had been setted in the /src/main/sources/logback.xml .
But when i submit the topology to storm cluster ,i found the logback.xml in the
topology became
invalid and the log message about topology was wrote to the
$STORM_DIR/logs/worker-xxx.log files
which are setted in the $STORM_DIR/logback/cluster.xml or
$STORM_DIR/logback/worker.xml ranther
than my file.
So,how to solve the problem?
And how to configure different logback.xml for different topology?
Note : The premise is not to modify the cluster.xml or worker.xml in the
$STORM_DIR/logback
regards,
devopts
