ashwindakappagari commented on issue #25936:
URL: https://github.com/apache/pulsar/issues/25936#issuecomment-4626030895
Thanks @lhotari — agree on the one-liner approach.
One question: the residual gap where producer creation succeeds slightly
past operationTimeoutMs is exactly the bug class we're fixing, just narrower.
In environments where broker pod replacement DNS recovery can exceed 30s (we
observed 12s, but tail latencies during AZ-spanning rollouts have been seen
higher), the orphan can still form.
Would you be open to additionally applying a whenComplete-style cleanup on
the residual future? Diff is +5 lines on top of your one-liner, eliminates the
gap entirely. Otherwise, would you recommend tuning operationTimeoutMs upward
as the documented mitigation for environments at risk?
Hope thats a fair Q.
Appreciate your quick response.
--
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]
