[ https://issues.apache.org/jira/browse/KAFKA-14285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Chen resolved KAFKA-14285. ------------------------------- Fix Version/s: 3.4.1 3.5.0 Resolution: Fixed > Delete quota node in zookeeper when configs are empty > ----------------------------------------------------- > > Key: KAFKA-14285 > URL: https://issues.apache.org/jira/browse/KAFKA-14285 > Project: Kafka > Issue Type: Improvement > Components: core > Affects Versions: 1.1.0, 2.7.1, 3.3.1 > Reporter: Junyang Liu > Assignee: Junyang Liu > Priority: Major > Fix For: 3.4.1, 3.5.0 > > > When configuring flow control quota for users and clients, Kafka will add a > child node to /config/users or /config/clients in zookeeper. When deleting a > flow control quota config, the existing node in zookeeper will not be deleted > even if the configs in the node are empty. So if a client repeatedly > configure and delete flow control quota for different users and clients, the > node in zookeeper will increase continuously, which may leads to severe > problems such as memory leak. -- This message was sent by Atlassian Jira (v8.20.10#820010)