-
Notifications
You must be signed in to change notification settings - Fork 233
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
catch "NodeNotReadyError" exception while consuming from Kafka #612
Comments
At the moment there is no way to catch connection errors, sorry. What situation in particular are you interested in? When some node disconnects or is not reachable for some amount of time, or all nodes are not available? |
@tvoinarovskyi can it automatically connect with other active nodes when few nodes are down? Our system just hangs when one node is down. |
@ja8zyjits It should, the system is meant to run on cluster systems with automatic reconnect on node failure. Could you open a bug issue with more detail on what scenario are you seeing? There seems to be one issue #625, that also has symptoms of stopping, maybe it may be related. |
@tvoinarovskyi sorry, not able to reproduce. It happens rarely and the system just hangs. |
If you have two containers one I tried a lot of different approaches, setting lower times for the session, consumer and other things but none of them worked. |
Anyone able to fix the issue yet"? |
Still having the issue. |
Hey can we catch "NodeNotReadyError" exception while consuming from Kafka . So that we can take any action at this situation. Like sending alert.
The text was updated successfully, but these errors were encountered: