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

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2022/08/14 15:23:56 UTC

[GitHub] [pulsar] Raven888888 commented on issue #17024: [Bug] Brokers in a cluster become unhealthy collectively

Raven888888 commented on issue #17024:
URL: https://github.com/apache/pulsar/issues/17024#issuecomment-1214400407

   Thanks for your input @lhotari @HQebupt 
   
   Though do we have any bug fixes on broker stability from 2.7.0 to 2.7.4/5?
   
   Often when the brokers in the cluster become unhealthy, and we try to restart them, they *always* hit this exception
   ```
   15:14:43.615 [main] ERROR org.apache.pulsar.functions.worker.WorkerService - Error Starting up in worker
   ```
   Which sometimes is due to `timeout`, or `connection refused` when connecting to other brokers. What we always end up doing, is shutting off external traffic at proxy level, and let the brokers recover first. For some reasons, brokers unable to startup when there is high external traffic.
   
   Have you encountered similar issue before? This seems to happen to pulsar function enabled broker.


-- 
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: commits-unsubscribe@pulsar.apache.org

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