You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the message producer to send a message, providing a delivery channel and then I block on the channel, waiting for the result.
I've noticed that when the target Kafka server is unavailable, instead of returning an error on the delivery channel, the client seems to retry to connect to the server forever.
My application is non blocking and needs to know quickly (within a few ms) whether the produce succeeded or failed, so it can go and do other stuff.
I've tried to configure "reconnect.backoff.ms", "reconnect.backoff.max.ms" and "retry.backoff.ms" but these don't seem to have any effect.
Can you tell me how to configure the client so it doesn't retrying connecting and returns an error straightaway?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I am using the message producer to send a message, providing a delivery channel and then I block on the channel, waiting for the result.
I've noticed that when the target Kafka server is unavailable, instead of returning an error on the delivery channel, the client seems to retry to connect to the server forever.
My application is non blocking and needs to know quickly (within a few ms) whether the produce succeeded or failed, so it can go and do other stuff.
I've tried to configure "reconnect.backoff.ms", "reconnect.backoff.max.ms" and "retry.backoff.ms" but these don't seem to have any effect.
Can you tell me how to configure the client so it doesn't retrying connecting and returns an error straightaway?
Beta Was this translation helpful? Give feedback.
All reactions