Topic deletion is much more simple in KRaft since it uses a log for all metadata operations. We have a RemoveTopic record which now indicates the deletion of a topic based on topic ID. In ZK mode, we rely on the controller to push metadata to specific brokers based on assignments. In KRaft, all brokers fetch all of the cluster metadata, so we have much more predictable behavior and a uniform view of the state of the cluster.
I'm not familiar with that specific issue you linked, but I do know we have had many problems with pending deletions in the past with ZK mode. So far, we have seen far fewer issues in KRaft. HTH David On Wed, Nov 5, 2025 at 1:43 PM meovh <[email protected]> wrote: > Hello, > > I encountered a problem when trying to delete and then recreate a topic on > a cluster (zk-brokers, Kafka 3.9.1) on which a broker was shut down. > > When trying to recreate the topic, I got the following error: > > > Error while executing topic command: Topic ‘mytopic’ is marked for > deletion. > > After little research, I came across this issue, which is still open on > Jira: https://issues.apache.org/jira/browse/KAFKA-5200 > > I tried to reproduce this issue on a cluster also running 3.9.1, but in > kraft mode, and I was able to delete and recreate the topic without any > problems. Has this issue been resolved with kraft? > > Have a nice day, > Maxime -- -David
