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
Is your feature request related to a problem? Please describe.
I am attempting to solve an issue with Azure EventHub, where we are seeing intermittent ECONNRESET and ETIMEDOUT errors. I came across another Kafka Library that seems to make claims about Azure closing idle connections. The library recommends setting the metadata.max.age.ms and connections.max.idle.ms configurations.
In KafkaJS, I found metadataMaxAge on the consumer and producer configs, so I set those accordingly. The problem still remained. I think I might need to set connections.max.idle.ms, but I cannot figure out how to set that in KafkaJS.
Describe the solution you'd like
Some way to set the connections.max.idle.ms configuration.
I'm also open to other suggestions if anyone has experienced this issue with EventHub.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am attempting to solve an issue with Azure EventHub, where we are seeing intermittent ECONNRESET and ETIMEDOUT errors. I came across another Kafka Library that seems to make claims about Azure closing idle connections. The library recommends setting the
metadata.max.age.ms
andconnections.max.idle.ms
configurations.In KafkaJS, I found
metadataMaxAge
on the consumer and producer configs, so I set those accordingly. The problem still remained. I think I might need to setconnections.max.idle.ms
, but I cannot figure out how to set that in KafkaJS.Other library for reference: https://github.com/Azure/azure-event-hubs-for-kafka/blob/master/CONFIGURATION.md#producer-and-consumer-configurations
Describe the solution you'd like
Some way to set the
connections.max.idle.ms
configuration.I'm also open to other suggestions if anyone has experienced this issue with EventHub.
The text was updated successfully, but these errors were encountered: