out_kafka2: Broker pool to take care of fetching metadata #503
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.
Which issue(s) this PR fixes:
#502
What this PR does / why we need it:
On enabling the get_kafka_client_log true, this can be figured out the leader of partitions is being queried multiple times: here
this metadata if refreshed by broker pool (here). Adding this in producer would resolve the issue.
additionally, this is a part of an optimisation done on ruby-kafka.
Test cases passing post the changes.
Docs Changes:
NA