[
https://issues.apache.org/jira/browse/KAFKA-16003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797215#comment-17797215
]
David Arthur edited comment on KAFKA-16003 at 12/15/23 2:54 PM:
----------------------------------------------------------------
Ah, great! Thanks again for the report [~ppatierno].
[~mimaison] thanks for picking this one up. I did look into it briefly
yesterday and I think the simplest thing is to create the znode in in
ZkTopicMigrationClient#createTopic when we create the main topic ZNode. The
topic configs (if any) will later get written by ZkConfigMigrationClient.
was (Author: davidarthur):
Ah great. Thanks again for the report [~ppatierno].
[~mimaison] thanks for picking this one up. I did look into it briefly
yesterday and I think the simplest thing is to create the znode in in
ZkTopicMigrationClient#createTopic when we create the main topic ZNode. The
topic configs (if any) will later get written by ZkConfigMigrationClient.
> The znode /config/topics is not updated during KRaft migration in
> "dual-write" mode
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-16003
> URL: https://issues.apache.org/jira/browse/KAFKA-16003
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 3.6.1
> Reporter: Paolo Patierno
> Assignee: Mickael Maison
> Priority: Major
>
> I tried the following scenario ...
> I have a ZooKeeper-based cluster and create a my-topic-1 topic (without
> specifying any specific configuration for it). The correct znodes are created
> under /config/topics and /brokers/topics.
> I start a migration to KRaft but not moving forward from "dual write" mode.
> While in this mode, I create a new my-topic-2 topic (still without any
> specific config). I see that a new znode is created under /brokers/topics but
> NOT under /config/topics. It seems that the KRaft controller is not updating
> this information in ZooKeeper during the dual-write. The controller log shows
> that the write to ZooKeeper was done, but not everything I would say:
> {code:java}
> 2023-12-13 10:23:26,229 TRACE [KRaftMigrationDriver id=3] Create Topic
> my-topic-2, ID Macbp8BvQUKpzmq2vG_8dA. Transitioned migration state from
> ZkMigrationLeadershipState{kraftControllerId=3, kraftControllerEpoch=7,
> kraftMetadataOffset=445, kraftMetadataEpoch=7,
> lastUpdatedTimeMs=1702462785587, migrationZkVersion=236, controllerZkEpoch=3,
> controllerZkVersion=3} to ZkMigrationLeadershipState{kraftControllerId=3,
> kraftControllerEpoch=7, kraftMetadataOffset=445, kraftMetadataEpoch=7,
> lastUpdatedTimeMs=1702462785587, migrationZkVersion=237, controllerZkEpoch=3,
> controllerZkVersion=3}
> (org.apache.kafka.metadata.migration.KRaftMigrationDriver)
> [controller-3-migration-driver-event-handler]
> 2023-12-13 10:23:26,229 DEBUG [KRaftMigrationDriver id=3] Made the following
> ZK writes when handling KRaft delta: {CreateTopic=1}
> (org.apache.kafka.metadata.migration.KRaftMigrationDriver)
> [controller-3-migration-driver-event-handler] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
