you have to modifiy all storm/logback/cluster.xml on all workers and remove all work-* files under logs, then it should work. If not, please check if there is logback.xml in your jar which might take first priority. Let me know if you still have any issue.
2015-07-02 8:36 GMT+08:00 임정택 <[email protected]>: > - Did your workers restarted after changing log level? > - Could you check your workers to have -Dlogback.configurationFile option, > and it's pointing to modified file? > > > 2015-07-02 9:04 GMT+09:00 张炜 <[email protected]>: > >> Thanks a lot, 임정택. >> >> It's my my bad: This is also set but I missed pasting it. >> >> <root level="WARN"> >> <appender-ref ref="A1"/> >> </root> >> >> >> Also I restarted storm after I change the settings. >> >> What else could be the problem? >> >> Regards, >> Sai >> >> On Thu, Jul 2, 2015 at 8:00 AM, 임정택 <[email protected]> wrote: >> >>> Hi, >>> >>> You have to modify root logger tag's level to WARN to make your >>> worker write less logs. >>> >>> <root level="WARN"> >>> >>> >>> Normally you don't need to adjust access / metrics logger's level cause >>> it is relatively small. >>> >>> Hope this helps. >>> >>> Thanks, >>> Jungtaek Lim (HeartSaVioR) >>> >>> >>> 2015-07-02 8:50 GMT+09:00 张炜 <[email protected]>: >>> >>>> Hi all, >>>> Storm is really putting a lot of information so it's hard to find our >>>> own messages. >>>> I have used slf4j logger to log the message that I want to track, at >>>> level WARN and ERROR. >>>> >>>> What I have done to configure in Storm is: >>>> 1). in topology setDebug(false) >>>> 2) in storm/logback/cluster.xml change level from INFO to WARN >>>> >>>> <logger name="backtype.storm.security.auth.authorizer" >>>> additivity="false"> >>>> <level value="WARN" /> >>>> <appender-ref ref="ACCESS" /> >>>> </logger> >>>> >>>> <logger name="backtype.storm.metric.LoggingMetricsConsumer" >>>> additivity="false" > >>>> <level value="WARN"/> >>>> <appender-ref ref="METRICS"/> >>>> </logger> >>>> >>>> But it doesn't work. Storm is stilling writing a lot of info level info >>>> in worker-6703.log for example: >>>> >>>> 2015-07-01T01:40:39.305+0000 s.k.ZkCoordinator [INFO] Task [4/7] Deleted >>>> partition managers: [] >>>> 2015-07-01T01:40:39.305+0000 s.k.ZkCoordinator [INFO] Task [4/7] New >>>> partition managers: [] >>>> 2015-07-01T01:40:39.305+0000 s.k.ZkCoordinator [INFO] Task [4/7] Finished >>>> refreshing >>>> 2015-07-01T01:41:39.311+0000 s.k.ZkCoordinator [INFO] Task [4/7] >>>> Refreshing partition manager connections >>>> 2015-07-01T01:41:39.454+0000 s.k.DynamicBrokersReader [INFO] Read >>>> partition info from zookeeper: GlobalPartitionInformation >>>> 2015-07-01T01:41:39.455+0000 s.k.ZkCoordinator [INFO] Task [4/7] Finished >>>> refreshing >>>> >>>> Could anyone kindly let me know what's the right way to configure the >>>> log level in Storm? >>>> >>>> Regards, >>>> Sai >>>> >>>> >>> >>> >>> -- >>> Name : 임 정택 >>> Blog : http://www.heartsavior.net / http://dev.heartsavior.net >>> Twitter : http://twitter.com/heartsavior >>> LinkedIn : http://www.linkedin.com/in/heartsavior >>> >> >> >> >> -- >> 流水不争先o00 >> > > > > -- > Name : 임 정택 > Blog : http://www.heartsavior.net / http://dev.heartsavior.net > Twitter : http://twitter.com/heartsavior > LinkedIn : http://www.linkedin.com/in/heartsavior > -- Best Regards, *Kevin Xu*
