hangc0276 commented on issue #15859: URL: https://github.com/apache/pulsar/issues/15859#issuecomment-1159889696
> For reducing broker load that broker will trigger healthCheck at regular intervals and collect the result @coderzc Does the `healthCheck` operation on the broker side triggered by the broker itself? As you described, using plan A will only detect the requested broker, and check whether the broker is healthy or not. If the Pulsar cluster has 1000 brokers, and all the clients connect to the broker by serviceUrl, which only configured three brokers. It means only the three brokers will receive `healthCheck` requests, the other 997 brokers are idle in dealing with `healthCheck` requests. IMO, the `healthCheck` service on broker side is `trigger by client + regular check by broker` is better. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
