-
Notifications
You must be signed in to change notification settings - Fork 896
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
Automatically destory/recreate consumer client when connection is stale #899
Comments
Intended behavior is the client should automatically recover from all problems where it's possible to do so. If it doesn't then there's a bug. I'm not 100% sure if there's any known outstanding issues related to this (there doesn't seem to be any related fixes post 1.4.0 in the librdkafka release notes). Any more information you can provide would be appreciated (debug logs, though they are very verbose, so difficult to get in prod if this is a very intermittent issue). |
This might be "produce/consume hang after partition goes away and comes back, such as when a topic is deleted and re-created." which is fixed in v1.4.2: |
ok I deployed 1.4.2 so hopefully that helps.. Ill have to wait and see if the issue appears again |
@tatianafrank Hello. I think i have the same issue in v1.4.2. Does the issue be fixed after version up? |
Saw this error a few times before the connection went stale again |
Description
I have a script that runs an infinite while loop that continually consumes messages from a kafka topic using v1.4 of the confluent-kafka library. Sometimes, either due to too many connection timeout errors or some unknown issue, I will need to stop/restart the entire script so that the kafka client object can be destroyed/recreated and start working again. My question is if there is a dynamic way to detect when the client object needs to be recreated in the code without having to manually detect, stop, restart the entire script.
How to reproduce
Checklist
Please provide the following information:
confluent_kafka.version()
andconfluent_kafka.libversion()
): 1.4.0{...}
'debug': '..'
as necessary)The text was updated successfully, but these errors were encountered: