Consumers start hanging with AIOKafkaConnection._read() Cancelled Error
See original GitHub issueThe consumers start hanging at some point with the following error being logged:
[2017-11-07 18:17:47,547: ERROR] Task exception was never retrieved
future: <Task finished coro=<AIOKafkaConnection._read() done, defined at /home/foo/env/lib/python3.6/site-packages/aiokafka/conn.py:194> exception=CancelledError()>
What might be causing the error? Should we be crashing the consumer upon getting the error?
This is with aiokafka==0.3.1
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:16 (10 by maintainers)
Top Results From Across the Web
Top 5 aiokafka Code Examples - Snyk
To help you get started, we've selected a few aiokafka examples, based on popular ... _coordination_task.cancel() # disable for test try: await coordinator....
Read more >Consumer client — aiokafka 0.8.0 documentation
AIOKafkaConsumer transparently handles the failure of Kafka brokers and transparently adapts as topic partitions it fetches migrate within the cluster.
Read more >Jason Fried: If an asyncio Task fails in the woods and nobody ...
Its 3am you just got called about some asyncio production code that is failing either cryptically or silently. You discover that its using ......
Read more >The aiokafka from aio-libs - GithubHelp
KAFKA-3318: clean up consumer logging and error messages ... AIOKafkaConsumer): await consumer.start() await asyncio.sleep(1.1 * HEARTBEAT_INTERVAL) await ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ok, this is not the
idle
thing… Theconnections_max_idle_ms
config did not work at all =)Ohh, this is probably a fail on idle connection closure. The connection is closed if not active for some time, probably this log is a side effect there. Will investigate, thank