-
Notifications
You must be signed in to change notification settings - Fork 178
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
processor gets stuck in shutdown after error #176
Comments
frairon
added a commit
that referenced
this issue
Mar 8, 2019
The producer does not get canceled on rebalance. I think it should be then related to some error on emitting a message. Do you have the stack trace? |
Sorry, my bad. The example was just wrong.
|
frairon
added a commit
that referenced
this issue
Mar 14, 2019
TheL1ne
pushed a commit
that referenced
this issue
Aug 8, 2019
TheL1ne
pushed a commit
that referenced
this issue
Aug 8, 2019
frairon
added a commit
that referenced
this issue
Aug 12, 2019
frairon
added a commit
that referenced
this issue
Aug 12, 2019
frairon
added a commit
that referenced
this issue
Aug 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have seen cases where a running processor gets stuck while shutting down, when one of the brokers goes down or the metadata is changed due to e.g. rebalance.
The error is supposedly a
kafka.Promise
that is never finished, because the producer gets cancelled. This leads to the waitgroup in https://github.com/lovoo/goka/blob/master/partition.go#L142 to never get done, so the partition never shuts down, thus the whole processor gets stuck.We could not reproduce the bug, but a stack trace of one of the stuck processors showed this location.
PR is open, hope that will fix the issue.
The text was updated successfully, but these errors were encountered: