You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Kuan Po Tseng (Jira)" <ji...@apache.org> on 2025/07/30 16:13:00 UTC

[jira] [Created] (KAFKA-19566) Deprecate ClientQuotaCallback#updateClusterMetadata

Kuan Po Tseng created KAFKA-19566:
-------------------------------------

             Summary: Deprecate ClientQuotaCallback#updateClusterMetadata
                 Key: KAFKA-19566
                 URL: https://issues.apache.org/jira/browse/KAFKA-19566
             Project: Kafka
          Issue Type: Improvement
            Reporter: Kuan Po Tseng
            Assignee: Kuan Po Tseng


In KAFKA-18225, we discovered that {{ClientQuotaCallback#updateClusterMetadata}} is not supported in KRaft mode, unlike in Zookeeper mode. Kafka 4.0 addressed this gap by implementing the method, but limitations remain:
 * A new {{Cluster}} object (immutable and heavyweight) is passed on every metadata update, which may cause memory pressure in large clusters (see KAFKA-18239).

 * Some {{Cluster}} fields are confusing or irrelevant in KRaft, such as {{controller()}} returning a random node for compatibility. Also, listener parsing differs between modes, potentially causing inconsistent partition info (see KAFKA-19122).

To resolve these issues, *[KIP-1162|https://cwiki.apache.org/confluence/x/zInoF]* proposes a redesign of the method. However, given that this method remained unimplemented for years without user complaints, we believe it's not worth the complexity to fix it. Instead, we propose deprecating {{updateClusterMetadata}} now and removing it in Kafka 5.0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)