Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Socket disconnected

See original GitHub issue

After upgrade to kafka-python 1.3.1, I get these errors 2-5 times an hour:

<BrokerConnection host=HOST_NAME/1.2.3.4 port=9092>: socket disconnected

Based on just the error message, I’m not sure why this happens or does the producer lose messages or not.

Issue Analytics

State:
Created 7 years ago
Reactions:10
Comments:12 (3 by maintainers)

Top GitHub Comments

1reaction

dpkpcommented, Mar 9, 2017

BrokerConnection does not auto-retry, no. Retry logic is upstream and depends on exception type and context.

KafkaProducer retries failed requests up to a certain number of times, configured by retries.

KafkaConsumer will generally refresh metadata and retry – possibly to a new partition leader – when a broker connection fails.

1reaction

Xaeliascommented, Feb 28, 2017

I think this issue is causing random failures on my end too. I end up with my consumer seemingly healthy but not consuming anything. It shows as “rebalancing” for the broker (which I think is bug with them, it’s dead IMO). And it’s a pain because I don’t have a reliable way to detect it and at the very least spawn a new consumer…