-
Notifications
You must be signed in to change notification settings - Fork 1.4k
BrokerConnection | Error receiving network data closing socket #2111
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
Comments
Hi @takwas, I am having the same problem with Azure Event Hubs. In my logs I have seen it reconnect from this KafkaConnectionError, however if there is an error sending HeartBeatRequest_v1 to node coordinator it will stop reconnecting. Can I check with you what version of kakfa-python are you using? Reconnected:
Failed and stopped:
Can anyone shed a light why it doesn't attempt to reconnect after HeartbeatRequest_v1 failed to send? |
Hi, @Caisho. Thanks for sharing. I am using 2.0.1. |
This may be related to #1985... not sure, I haven't looked closely, but at first glance the sound similar. |
@jeffwidman: I think it is indeed quite similar, but mightn't be the exact same thing. That last comment by @mjattiot also reflects our situation. The unpleasant thing about this situation is that, the Kubernetes pod keeps running as if nothing has happened whereas it's in a deadlocked state. |
@dpkp, @jeffwidman: Any insights on this issue, please? It is now happening rather unpredictably, frequently and in such a silent way. One way to attempt reproducing this is to force-kill TCP connection, but I don't have all the details about the other factors that come to play. Based on the error logs shared by myself and @Caisho, the following portions of the codebase are of interest:
|
@jeffwidman: Having taken a closer look, I would surmise that this is indeed related to the case with #1985. With that thought, do you think that there will be a release with the changes in #2064 soon? |
We have a relatively new setup that uses the Kafka protocal over Azure Event Hubs. Our usage of the
KafkaConsumer
client largely uses the default configuration, except for:Everything has run fine until recently -- and only on one occasion -- when we found this in the log. It appears the app would only resume upon a restart.
In light of the above premise, I'd like to ask:
The text was updated successfully, but these errors were encountered: