PavelZeger commented on issue #1481:
URL:
https://github.com/apache/pulsar-client-go/issues/1481#issuecomment-4412191831
Thanks @nodece for the detailed analysis and the Java references!
Runtime reconnection in Go doesn't actually stop at max backoff — `opFn`
still returns `err`, so the retry loop continues indefinitely at the capped
interval. Only the metric was incremented. So that part already matches Java's
behavior.
That said, your point about the listener firing on `IsMaxBackoffReached` is
fair - it's a "max delay" signal, not a "give up" signal, and using it to
trigger auto-close would close the consumer way too early. I'll drop that
clause so the listener and auto-close fire only on the explicit `maxRetry == 0`
exhaustion, which keeps the new side effects scoped to users who opted into a
finite retry budget.
I've already pushed changes in this PR that touch this exact area - if they
cover what you have in mind, I'll apply the additional adjustment we discussed
(dropping the I`sMaxBackoffReached` clause); otherwise let me know what's still
missing and I'll align.
--
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]
