You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2021/03/23 06:14:18 UTC

[GitHub] [rocketmq] EZLippi opened a new issue #2746: too many info log for updating offset to broker

EZLippi opened a new issue #2746:
URL: https://github.com/apache/rocketmq/issues/2746


   too many info log when updating offset to broker use cluster mode consuming, and this log cannot be configure to print in a single file because all log for the client share the same log named RocketmqClient
   `43.857 INFO [MQClientFactoryScheduledThread:RocketmqClient] [persistAll] Group: cg__topic_rabbit-exchange-test_task ClientI`
   
   把日志的粒度降低一些, 这样也能差异化配置每个包的使用单独的日志级别和输出文件, 现在每隔5秒钟会打印很多info日志, 但又不想把级别改成warn, 只想把updateOffsettoBroker的日志级别改成warn.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] EZLippi commented on issue #2746: Too many info logs for updating offset to broker

Posted by GitBox <gi...@apache.org>.
EZLippi commented on issue #2746:
URL: https://github.com/apache/rocketmq/issues/2746#issuecomment-813959995


   > @EZLippi 这个问题确实比较会引起困扰，主要是一方面位点更新，对于问题定位非常重要，不仅仅需要看最新的一次上报的位点，也看趋势的变化。另外一个方面是，这个日志相对较多，目前从定位问题的角度，把这个日志设置成了info，而且没有多次打一次。
   > 您可以尝试着修改指定类的日志级别（google 一下logback 设置指定类日志级别），将 RemoteBrokerOffsetStore这个类的日志改为WARN
   
   
   
   > @EZLippi 这个问题确实比较会引起困扰，主要是一方面位点更新，对于问题定位非常重要，不仅仅需要看最新的一次上报的位点，也看趋势的变化。另外一个方面是，这个日志相对较多，目前从定位问题的角度，把这个日志设置成了info，而且没有多次打一次。
   > 您可以尝试着修改指定类的日志级别（google 一下logback 设置指定类日志级别），将 RemoteBrokerOffsetStore这个类的日志改为WARN
   
   不行吧, 你们这个日志不是通过类名来获取Logger的, 而是固定的名字RocketmqClient, 无法差异化配置每个类使用单独日志文件
   ![image](https://user-images.githubusercontent.com/5326814/113686880-52cba400-96fa-11eb-95f6-b79559f9dc3c.png)
   ![image](https://user-images.githubusercontent.com/5326814/113686911-5b23df00-96fa-11eb-86c8-d176df93b6cf.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] duhenglucky closed issue #2746: Too many info logs for updating offset to broker

Posted by GitBox <gi...@apache.org>.
duhenglucky closed issue #2746:
URL: https://github.com/apache/rocketmq/issues/2746


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [rocketmq] duhenglucky commented on issue #2746: Too many info logs for updating offset to broker

Posted by GitBox <gi...@apache.org>.
duhenglucky commented on issue #2746:
URL: https://github.com/apache/rocketmq/issues/2746#issuecomment-813950898


   @EZLippi 这个问题确实比较会引起困扰，主要是一方面位点更新，对于问题定位非常重要，不仅仅需要看最新的一次上报的位点，也看趋势的变化。另外一个方面是，这个日志相对较多，目前从定位问题的角度，把这个日志设置成了info，而且没有多次打一次。
   您可以尝试着修改指定类的日志级别（google 一下logback 设置指定类日志级别），将 RemoteBrokerOffsetStore这个类的日志改为WARN


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org