Closed benjamin99 closed 1 year ago
Instead of changing the value of MaxConnectionsPerBroker
of the current client, I think we should use a new client in the tracker.
Close the PR since it was the seek
command of the subscription tracker (before v0.0.46) that caused the reconnections, not the connection pool related issue.
Description
In the previous implementations, the subscription tracker will always triggered the reconnection process to the pulsar broker. To solve the issue, the PR adjusted the config of the connection pool size of the corresponding pulsar client to two.