You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2022/01/07 08:33:01 UTC

[GitHub] [apisix] guxingke edited a comment on issue #6033: bug: kafka-logger, always log `not found broker` after kafka-logger kafka broker up. until reload apisix.

guxingke edited a comment on issue #6033:
URL: https://github.com/apache/apisix/issues/6033#issuecomment-1007227481


   the kafka broken in other case .
   
   ---
   when i restart kafka borkers , and waiting the apisix send message auto recover. but not ,  about  5 minute later , relaod the apisix, it works well.
   
   ---
   > In my experience, the kafka producer has a lrucache, so you can update the kafka-logger configuration with the cluster_name parameter to generate a new kafka producer?
   
   Maybe in the next time, I will try this solution.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org

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