wolfstudy commented on PR #853: URL: https://github.com/apache/pulsar-client-go/pull/853#issuecomment-1260753669
> LGTM - just confirming that the backoff will be on both the consumer and producer config (it was a little confusing to me as in the Java library it is solely on the client https://github.com/apache/pulsar/blob/31203c3952dfb82057ac1fbee4efc10682a5570b/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ClientBuilderImpl.java#L319-L323 ) > > (And also thanks so much for the quick turnaround) Yes, this is where the current Go SDK design is worth optimizing. In the Go SDK, we implemented the reconnect logic to the Producer side and the Consumer side respectively, and did not abstract a unified reconnect logic at the Client level. This leads to the Backoff strategy, we can only divide it into ProducerOptions and ConsumerOptions. In the follow-up, I think we should refactor here and abstract the logic of reconnect to the client side, which is more reasonable -- 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]
