[Bug]: MMR2 Create topic with alias name + heartbeat if source have topic with name end ...heartbeats

[ldn7]

Bug Description

Source kafka cluster (prod) mmr2 create topic heartbeats, because it add new mmr2 between two clusters. So at source cluster add new topic heartbeats, target clusters create everyone topic alias+heartbeat example prod-to-preprod-source-heartbeats or prod-to-test-source-heartbeats. If at source cluster I create new topic with name prod-to-preprod-source-heartbeats, to target cluster mmr2 create topic prod-to-preprod-source-prod-to-preprod-source-heartbeats or prod-to-test-source-prod-to-preprod-source-heartbeats. I delete it topics, but mmr2s create it again. At logs [Scheduler for MirrorSourceConnector: prod-to-preprod-source->prod-to-preprod-target|prod-to-preprod-source->prod-to-preprod-target.MirrorSourceConnector-refreshing topics] MirrorSourceConnector:376 - Found 0 new topic-partitions on prod-to-preprod-source. Found 0 deleted topic-partitions on prod-to-preprod-source. Found 2 topic-partitions missing on prod-to-preprod-target. prod-to-preprod-source->prod-to-preprod-target|prod-to-preprod-source->prod-to-preprod-target.MirrorSourceConnector|replication-target-admin] MirrorSourceConnector:521 - Could not create topic prod-to-preprod-source-prod-to-preprod-source-heartbeats.
java.util.concurrent.CompletionException: org.apache.kafka.common.errors.TopicExistsException: Topic 'prod-to-preprod-source-prod-to-preprod-source-heartbeats' already exists Caused by: org.apache.kafka.common.errors.TopicExistsException: Topic 'prod-to-preprod-source-heartbeats' already exists.
it try create it, but topic always exist.
version 0.47.0
Help me please

Steps to reproduce

No response

Expected behavior

No response

Strimzi version

0.47.0

Kubernetes version

k8s v1.33.5

Installation method

helm strimzi-kafka-operator-0.47.0

Infrastructure

No response

Configuration files and logs

apiVersion: v1
items:

• apiVersion: kafka.strimzi.io/v1beta2
  kind: KafkaMirrorMaker2
  metadata:
  labels:
  app: lime-shine-prod-to-preprod
  name: lime-shine-prod-to-preprod
  namespace: strimzi
  spec:
  clusters:
  • alias: prod-to-preprod-source
    authentication:
    passwordSecret:
    password: source_password
    secretName: lime-shine-kafka-users-prod-to-preprod
    type: scram-sha-512
    username: admin
    bootstrapServers: prod-kafka-broker-0:9092,prod-kafka-broker-1:9092,prod-kafka-broker-2:9092
  • alias: prod-to-preprod-target
    authentication:
    passwordSecret:
    password: target_password
    secretName: lime-shine-kafka-users-prod-to-preprod
    type: scram-sha-512
    username: admin
    bootstrapServers: preprod-kafka-broker-0:9092,preprod-kafka-broker-1:9092,preprod-kafka-broker-2:9092
    config:
    config.storage.replication.factor: 3
    config.storage.topic: prod-to-preprod-configs
    group.id: prod-to-preprod
    offset.storage.replication.factor: 3
    offset.storage.topic: prod-to-preprod-offsets
    status.storage.replication.factor: 3
    status.storage.topic: prod-to-preprod-status
    connectCluster: prod-to-preprod-target
    image: quay-io/strimzi/kafka:0.47.0-kafka-4.0.0
    livenessProbe:
    initialDelaySeconds: 25
    timeoutSeconds: 25
    logging:
    loggers:
    connect.root.logger.level: INFO
    type: inline
    metricsConfig:
    type: jmxPrometheusExporter
    valueFrom:
    configMapKeyRef:
    key: metrics-config.yml
    name: kafka-mm2-metrics
    mirrors:
  • checkpointConnector:
    autoRestart:
    enabled: true
    config:
    checkpoints.topic.replication.factor: "3"
    emit.checkpoints.interval.seconds: "30"
    refresh.groups.interval.seconds: "60"
    replication.policy.class: org.apache.kafka.connect.mirror.IdentityReplicationPolicy
    replication.policy.separator: '-'
    sync.group.offsets.enabled: "false"
    sync.group.offsets.interval.seconds: "10"
    groupsPattern: .*
    heartbeatConnector:
    autoRestart:
    enabled: true
    config:
    emit.heartbeats.enabled: "true"
    heartbeats.topic.replication.factor: "3"
    replication.policy.class: org.apache.kafka.connect.mirror.IdentityReplicationPolicy
    replication.policy.separator: '-'
    sourceCluster: prod-to-preprod-source
    sourceConnector:
    autoRestart:
    enabled: true
    config:
    offset-syncs.topic.replication.factor: "3"
    refresh.topics.interval.seconds: "60"
    replication.factor: "3"
    replication.policy.class: org.apache.kafka.connect.mirror.IdentityReplicationPolicy
    replication.policy.separator: '-'
    sync.topic.acls.enabled: "false"
    sync.topic.configs.enabled: "false"
    tasksMax: 10
    targetCluster: prod-to-preprod-target
    topicsPattern: hr-individuals|hr-jobtitle|hr-hierarchy|enterprise-hierarchy|hr-employee
    readinessProbe:
    initialDelaySeconds: 25
    timeoutSeconds: 25
    replicas: 1
    resources:
    limits:
    memory: 2Gi
    requests:
    memory: 100Mi

Additional context

No response

[scholzj]

Please make sure to:

• Format things properly to make sure they are readable
• Make sure the issue you are opening is actually a Strimzi issue. Strimzi does not create any topics when deploying Mirror Maker 2. That is all done by Mirror Maker itself. So you either misconfigured it, or it is likely a Kafka bug. (+ keep in mind that you can simply disable the Heartbeat connector as it is mostly useless anyway)