I'm trying to finish the migration of a dev cluster that used to use ZK. I finished the migration of Metadata from ZK to raft and it completed fairly fast. I did notice an error message: * java.lang.RuntimeException: The log dir Log(dir=/opt/kafka/data/topics/ingestperf.ingest-perf.ania001.3fd04d61e150165a-0, topic=ingestperf.ingest-perf.ania001.3fd04d61e150165a, partition=0, highWatermark=0, lastStableOffset=0, logStartOffset=0, logEndOffset=190068) does not have a topic ID, which is not allowed when running in KRaft mode.
But it seemed that it was not causing the broker to crashloop and also it seemed that the migration from ZK to Kafka worked. Now that I just restarted the broker after entering the migration of the broker as described in *"**Migrating brokers to KRaft" *in https://kafka.apache.org/documentation/#kraft_zk_migration I'm seeing this issue one more time but also the broker keeps on crashing. I'm running Kafka 3.7.0 on the broker. Looking at https://github.com/apache/kafka/blob/trunk/core/src/main/scala/kafka/log/LogManager.scala#L1097 it seems that there is something to take care of this situation but it seems it's not working. I'm wondering how to get out of this situation. Is there a way to assign a topic ID to topics that don't have one ?, is there a way to list topics that don't have topic ID ? I'm thinking on this particular topic to use cruise control to migrate the topic to another broker in the hope that it would force the creation of a topic ID there (not sure tbh). Best. Matthieu.
