-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix cluster-wide Kafka client bug #14857
Fix cluster-wide Kafka client bug #14857
Conversation
Signed-off-by: chrismark <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if it's possible to cover these changes with an integration test or sth. Anyway, approved!
Signed-off-by: chrismark <[email protected]>
@mtojek thanks for reviewing! I checked about the test addition and I tuned a little bit the current one so as to |
Cool! Thanks for the heads up. |
(cherry picked from commit 6c279eb)
(cherry picked from commit 6c279eb)
This PR fixes a bug introduced on #14822.
The cluster-wide client was never re-opened after the first call to
Fetch
method because all the other times theConnect
method to broker was returning before the cluster-wide client initialisation, due tobeats/metricbeat/module/kafka/broker.go
Line 126 in 4f0b4f9
cc: @jsoriano @mtojek