Gilthoniel opened a new issue, #1272: URL: https://github.com/apache/pulsar-client-go/issues/1272
#### Expected behavior The client should properly handle a cluster that is not ready yet and retry until it gets healthy again. #### Actual behavior When the client is attempting to reconnect or to create new producers, consumers or readers but the service is not ready, it has a chance to block the connection pool. #### Steps to reproduce `ConnectionClosed` callbacks have a chance of blocking the connection pool because the `GetConnection` of the pool may close a connection when the state has changed, which happens when the cluster is not ready. In our case, we were observing a lot of closing because right after getting a connection to the broker, it was closing due to ServiceNotReady since too many bookies were down. #### System configuration **Pulsar version**: 3.0.5 **Pulsar client**: 13.1 -- 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]
