You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Karthik (Jira)" <ji...@apache.org> on 2020/06/09 11:36:00 UTC
[jira] [Updated] (KAFKA-10128) MM2 - Delete topics when config sync
is enabled
[ https://issues.apache.org/jira/browse/KAFKA-10128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karthik updated KAFKA-10128:
----------------------------
Reviewer: Ryanne Dolan
> MM2 - Delete topics when config sync is enabled
> -----------------------------------------------
>
> Key: KAFKA-10128
> URL: https://issues.apache.org/jira/browse/KAFKA-10128
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect, mirrormaker
> Affects Versions: 2.5.0
> Reporter: Karthik
> Priority: Minor
>
> Topics being deleted on one region is not being deleted and with that its being recreated incase of a active-active deployment
>
> Logs:
> *Test Check delete Topic*
>
> *Delete Command*
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.0.32:9092 --delete --topic im115
>
> *Source cluster - Before*
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.0.32:9092 --list
> __consumer_offsets
> heartbeats
> im115
> im32
> mm2-configs.us-east.internal
> mm2-offset-syncs.us-east.internal
> mm2-offsets.us-east.internal
> mm2-status.us-east.internal
> us-east.checkpoints.internal
> us-east.heartbeats
> us-east.im115
> us-east.us-east-offsets
> us-west-offsets
>
> *Source cluster -* *After delete*
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.0.32:9092 --list
> __consumer_offsets
> heartbeats
> im32
> mm2-configs.us-east.internal
> mm2-offset-syncs.us-east.internal
> mm2-offsets.us-east.internal
> mm2-status.us-east.internal
> us-east.checkpoints.internal
> us-east.heartbeats
> us-east.im115
> us-east.us-east-offsets
> us-west-offsets
>
> *Dest Cluster - Before*
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.3.115:9092 --list __consumer_offsets
> heartbeats
> im115
> mm2-configs.us-west.internal
> mm2-offset-syncs.us-west.internal
> mm2-offsets.us-west.internal
> mm2-status.us-west.internal
> us-east-offsets
> us-west.checkpoints.internal
> us-west.heartbeats
> us-west.im115
> us-west.im32
> us-west.us-west-offsets
> **
> *Dest Cluster -* *After Delete*
> *Did not delete*
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.3.115:9092 --list __consumer_offsets
> heartbeats
> im115
> mm2-configs.us-west.internal
> mm2-offset-syncs.us-west.internal
> mm2-offsets.us-west.internal
> mm2-status.us-west.internal
> us-east-offsets
> us-west.checkpoints.internal
> us-west.heartbeats
> us-west.im115
> us-west.im32
> us-west.us-west-offsets
>
> With that after the config refresh mins, the deleted topic is being replicated back on the source cluster
> /opt/kafka/bin/kafka-topics.sh --bootstrap-server 192.168.0.32:9092 --list
> __consumer_offsets
> heartbeats
> im115
> im32
> mm2-configs.us-east.internal
> mm2-offset-syncs.us-east.internal
> mm2-offsets.us-east.internal
> mm2-status.us-east.internal
> us-east.checkpoints.internal
> us-east.heartbeats
> us-east.im115
> us-east.us-east-offsets
> us-west-offsets
--
This message was sent by Atlassian Jira
(v8.3.4#803005)