[
https://issues.apache.org/jira/browse/KAFKA-18225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911012#comment-17911012
]
Chia-Ping Tsai commented on KAFKA-18225:
----------------------------------------
We've opened a pull request (https://github.com/apache/kafka/pull/18196) to
address this issue. We expect to complete it this week and backport it to the
4.0 branch.
Additionally, KAFKA-18239 will propose a KIP to introduce a new API that
eliminates the need for the expensive Cluster class. This new API will be
exclusive to the 4.1 release.
> ClientQuotaCallback#updateClusterMetadata is unsupported by kraft
> -----------------------------------------------------------------
>
> Key: KAFKA-18225
> URL: https://issues.apache.org/jira/browse/KAFKA-18225
> Project: Kafka
> Issue Type: Task
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Blocker
> Fix For: 4.0.0
>
>
> `ClientQuotaCallback#updateClusterMetadata` is invoked by
> `KafkaAPIs#handleUpdateMetadataRequest` only. However, that is a zk-only API
> and hence, `updateClusterMetadata` is never executed in kraft mode. That
> brings two issues:
> 1. CustomQuotaCallbackTest needs to be rewritten hugely in order to migrate
> to kraft
> 2. Should we deprecate `updateClusterMetadata` directly in 4.0? or make it
> work on kraft mode or introduce new API to replace it
> Regardless to '2', we can enhance `DynamicClientQuotaPublisher` to support
> `ClientQuotaCallback#updateClusterMetadata` when handling `newImage`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
