Hi Colin, thanks for your response. Regards your point that the topic gets deleted immediately, I got that we do this if the cluster is healthy. However, if there's a hardware failure with the disk or the broker is unreachable and has a replica; In these cases, deleting the log files from the failed disk or unreachable broker will be impossible to delete until we fix the hardware issue, So during troubleshooting, how will we know which topic is stuck for deletion because we can't delete some replicas because of hardware failures?
Thanks On Mon, Nov 1, 2021 at 8:57 PM Colin McCabe <cmcc...@apache.org> wrote: > Hi Omnia, > > It is not necessary to know which topics are marked for deletion in when > in KRaft mode, because topic deletion happens immediately. > > best, > Colin > > On Thu, Oct 28, 2021, at 06:57, Omnia Ibrahim wrote: > > Hi, > > > > Kafka topicCommand used to report which topic is marked for deletion by > > checking the znode on zookeeper; this feature has been deprecated without > > replacement as part of KAFKA-12596 Remove deprecated --zookeeper in > > topicCommands <https://issues.apache.org/jira/browse/KAFKA-12596>. > > > > Also as far as I can see, there's no equivalent for this with KIP-500 as > > well. > > > > Is there any other way to know the state of deletion for Kafka with ZK > and > > Without ZK? > > > > Is possible to leverage `RemoveTopicRecord` on the metadata topic to > > provide the same feature? > > > > > > Thanks > > > > Omnia >
