Unable to react to errors during consumer disconnect
See original GitHub issueThe Consumer disconnect()
method (and the stop()
method it calls) swallows errors, making it hard to know when a consumer hasn’t cleaned disconnected. Instrumentation in the catch-blocks and/or resolving the promise with the error have both been mentioned in slack as options for bubbling these errors up.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Hi, our kafka applications got disconnection errors during ...
But Kafka go client apps started to throw disconnection errors and tried to reconnect, but it got refusing connection errors. Wondering is there ......
Read more >Kafka consumer reconnection after getting disconnected
kafka.common.errors.DisconnectException. I haven't configured the consumers in terms of reconnection. I know that there are two properties from ...
Read more >11 Ways to Fix the ERR_CONNECTION_TIMED_OUT Error
Solution 1: Restart Your Internet Connection ... There's a good chance you'll run into this issue, especially if there's a major internet outage....
Read more >Handling operation errors - Apollo GraphQL Docs
Apollo Client helps you handle these errors according to their type, enabling you to show appropriate information to the user when an error...
Read more >How to Fix the ERR_CONNECTION_RESET Error in 7 Ways
1. Check If the Website Is Working · 2. Disconnect from VPN · 3. Reboot Your Network Device · 4. Clear the Browser...
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
I would say that making disconnect throw the error might be a good place to start. That’s the most natural, least surprising, solution I can think of. Once we have a PoC implementation it might become clearer if there are any additional implications that require a different solution.
Feel free to contribute a pull request if you are interested. I’m currently on vacation and will soon not have access to a computer, but we try to be as responsive to PRs as we can, so we’ll help you out as needed.
Yep, good by me.