[
https://issues.apache.org/jira/browse/KAFKA-17663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17663.
------------------------------------
Fix Version/s: 4.0.0
Resolution: Fixed
> Add Metadata caching in admin.internals.PartitionLeaderStrategy
> ---------------------------------------------------------------
>
> Key: KAFKA-17663
> URL: https://issues.apache.org/jira/browse/KAFKA-17663
> Project: Kafka
> Issue Type: Improvement
> Components: admin
> Reporter: Nicolas Guyomar
> Assignee: Andrew Schofield
> Priority: Major
> Fix For: 4.0.0
>
>
> Hi team,
> To the best of my knowledge, there is no Metadata caching in AdminClient
> admin.internals.PartitionLeaderStrategy, and for use cases that keep long
> live AdminClient running with scheduled invocation of method such as the
> listOffsets, we could keep reusing the same Metadata and not request fresh
> one on each invocation
> This is particularly true when the listOffsets is invoked for monitoring
> purpose, often querying a high number of partitions at the same time, leading
> to rather "large" Metadata requests to be processed on the cluster side
> Thank you
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
