-
Notifications
You must be signed in to change notification settings - Fork 138
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
Consumer doesn't consume after onLost
#1288
Comments
onLost
onLost
For now, your options are:
|
Correction: #1252 is already part of zio-kafka 2.8.0, so something else is going on. |
The newest log line (first line) indicates that no partitions ( Can you check the java consumer configurations? |
The settings are almost default. Things we changed are |
When the broker is down, the consumer loses connection to the broker, and tries to reconnect, then
onLost
happens and after that runloop will never callpoll()
, so there are no new events. Is it a desired behavior? If yes, then how to restart consumer whenonLost
happens? (Last event was consumed at 20:08). Also in the application there are two consumer groups and they read the same topic (in parallel); one fails (onLost
happens), one continues to work (onLost
doesn't happen, since it's connected to a broker that doesn't go down).Related #1250. Version: 2.8.0.
Logs (the first message — the newest)
The text was updated successfully, but these errors were encountered: