Cherry-pick #14857 to 7.x: Fix cluster-wide Kafka client bug #14861
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #14857 to 7.x branch. Original message:
This PR fixes a bug introduced on #14822.
The cluster-wide client was never re-opened after the first call to
Fetchmethod because all the other times theConnectmethod to broker was returning before the cluster-wide client initialisation, due tobeats/metricbeat/module/kafka/broker.go
Line 126 in 4f0b4f9
cc: @jsoriano @mtojek