Open jsolana opened 3 years ago
If I recover the conectivity I have to wait as much 120 seconds (when the next Connection time out happend) and then Flush execution can finish (the message is produced) and continue.
I have not looked into this in detail, but reconnect.backoff.max.ms
is 10000, so I would expect the maximum time you should need to wait would be of that order (not 120 seconds). @edenhill ?
Description
Hi all,
I have an app, producing messages. This is the code:
Other producer configuration parameters (sasl configuration omited):
Environment
How to reproduce
I want to confirm if this is the expected behavior : 1) I establish connection between client and brokers 2) When I produce the message (just before), I lost the connectivity (I force this situation shutingdown VPN connection) and then continue the execution 3) The thread still waiting in Flush method. 3) Each 10 seconds a REQTMOUT message is printed 4) Each 120 seconds producerBuilder.SetErrorHandler code is execute with a connection timeout error
This is the log:
If I recover the conectivity I have to wait as much 120 seconds (when the next Connection time out happend) and then Flush execution can finish (the message is produced) and continue.
I asume that this interval between Connection timed out (after 129869ms in state CONNECT, 1 identical error(s) suppressed) and the connection recovery is configured with delivery.timeout.ms. Am I right or exists other form to configure connection timeout?
Thanks,
Checklist
Please provide the following information: