Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is connections.max.idle.ms a Consumer Configuration? #1544

Closed
cdemi opened this issue Mar 1, 2021 · 8 comments
Closed

Is connections.max.idle.ms a Consumer Configuration? #1544

cdemi opened this issue Mar 1, 2021 · 8 comments

Comments

@cdemi
Copy link

cdemi commented Mar 1, 2021

According to the Confluent Consumer Configuration Docs, connections.max.idle.ms should be available as a consumer configuration.

However it looks like this is not configurable on the Consumer Configuration side in this library? To be honest it doesn't look like librdkafka exposes this as well, so I'm wondering if the Confluent Consumer Configuration Doc is correct.

@mhowlett
Copy link
Contributor

mhowlett commented Mar 1, 2021

they are incorrect in that they imply the java client config applies to all clients, which is not the case. thanks.

@cdemi
Copy link
Author

cdemi commented Mar 1, 2021

Aha, I see. Would you consider a pull request to include this in this .NET Client if we figure out how? :)

@mhowlett
Copy link
Contributor

mhowlett commented Mar 1, 2021

why do you need this? note that on the broker there is connections.max.idle.ms (defaults to 10 minutes).

@cdemi
Copy link
Author

cdemi commented Mar 1, 2021

My usecase is this, let's imagine that my Kafka broker lives on premises. I have my broker connections.max.idle.ms set to 45 minutes because it's OK for my environment.

However a third-party client is consuming from Azure which the firewall idle timeout is about 4 minutes. If he is unable to configure it from the client-side our connection will keep a 45 minute idle timeout.

So my reasoning is this, as the Kafka Broker "hoster" we can never be sure of what the client's firewall policies are and we need them to be able to configure this on their end, because otherwise we would have to set an extremely low value for connections.max.idle.ms on the broker.

What do you think?

@mhowlett
Copy link
Contributor

mhowlett commented Mar 1, 2021

interesting point. related: confluentinc/librdkafka#3109

can I suggest opening an issue on librdkafka (it would be a librdkafka change), and let's see what @edenhill thinks about it.

@edenhill
Copy link
Contributor

edenhill commented Mar 9, 2021

connections.max.idle.ms will be available in the next librdkafka release.

@mhowlett
Copy link
Contributor

mhowlett commented Mar 9, 2021

thanks @edenhill !

@mhowlett mhowlett closed this as completed Mar 9, 2021
@cdemi
Copy link
Author

cdemi commented Mar 9, 2021

Thanks both @edenhill and @mhowlett. Really appreciate you spending the time and effort!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants