You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2024/03/21 14:41:00 UTC
[jira] [Resolved] (KAFKA-16206) KRaftMigrationZkWriter tries to delete deleted topic configs twice
[ https://issues.apache.org/jira/browse/KAFKA-16206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Maison resolved KAFKA-16206.
------------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> KRaftMigrationZkWriter tries to delete deleted topic configs twice
> ------------------------------------------------------------------
>
> Key: KAFKA-16206
> URL: https://issues.apache.org/jira/browse/KAFKA-16206
> Project: Kafka
> Issue Type: Bug
> Components: kraft, migration
> Reporter: David Arthur
> Assignee: Alyssa Huang
> Priority: Minor
> Fix For: 3.8.0
>
>
> When deleting a topic, we see spurious ERROR logs from kafka.zk.migration.ZkConfigMigrationClient:
>
> {code:java}
> Did not delete ConfigResource(type=TOPIC, name='xxx') since the node did not exist. {code}
> This seems to happen because ZkTopicMigrationClient#deleteTopic is deleting the topic, partitions, and config ZNodes in one shot. Subsequent calls from KRaftMigrationZkWriter to delete the config encounter a NO_NODE since the ZNode is already gone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)