You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "James Cheng (Jira)" <ji...@apache.org> on 2026/02/24 01:26:00 UTC

[jira] [Commented] (KAFKA-8180) Deleting large number of topics can block the controller for the time it takes to delete all of them

    [ https://issues.apache.org/jira/browse/KAFKA-8180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18060523#comment-18060523 ] 

James Cheng commented on KAFKA-8180:
------------------------------------

[KIP-599|https://cwiki.apache.org/confluence/display/KAFKA/KIP-599%3A+Throttle+Create+Topic%2C+Create+Partition+and+Delete+Topic+Operations] shipped as [KAFKA-9915|https://issues.apache.org/jira/browse/KAFKA-9915] as part of [Kafka 2.7.0|https://archive.apache.org/dist/kafka/2.7.0/RELEASE_NOTES.html]

We can close this JIRA.



> Deleting large number of topics can block the controller for the time it takes to delete all of them
> ----------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-8180
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8180
>             Project: Kafka
>          Issue Type: Bug
>          Components: controller
>            Reporter: Gwen Shapira
>            Priority: Major
>
> Scenario:
> - Create large number of topics (In my experiment: 400 topics with 12 partitions each )
> - Use the admin client to delete all of them in a single batch operation
> - Try to bounce another broker while this is going on
> As you can see from the logs and metrics - topic deletion happens synchronously in the controller and it does not do anything else (leader elections for instance) while it is busy deleting (which can take many minutes for large batches).
> I recommend fixing it by throttling the deletes - no matter how large a batch the client sent, the controller should delete a subset and complete a full cycle before deleting the next subset.



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