-
Notifications
You must be signed in to change notification settings - Fork 83
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
InstanceAlreadyExistsException with new multi-threaded consumer #175
Comments
Does consuming fail to work, or are you just seeing these errors but consuming works OK? When I saw those errors locally, it was because the parallel consumers were attempting to register the same JMX bean, and you'd get this error in the log. As far as I could determine from reviewing Kafka's consumer configurations, there was no way to prevent the JMX Metric Reporter from being registered. Consuming would work correctly however. |
You're right. I mistakenly thought consuming didn't work. But, it actually does. |
Glad to hear it actually works. The flood of errors are far from ideal, I'll try to put together a patch here shortly that works out a way to avoid them. |
Fix for this should be included in upcoming 2.3.1 release. Thanks! |
released 2.4.0 which should resolve those errors from being shown. Thanks! |
The new multi-threaded consumer in 2.3.0 doesn't seem to work for me. I just get unending errors in the logs for
InstanceAlreadyExistsException
. SettingmultiThreadedConsumer: false
in the config file works.The text was updated successfully, but these errors were encountered: