You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by "Peri, Viswanadh" <vp...@deloitte.com> on 2020/06/19 05:29:50 UTC

Apache MirrorMaker2 Issue

Hi All,

I am looking for an help to resolve a MirrorMaker2 issue. Here is the exception I am receiving at the kafka connect end during launch.


2020-06-19 05:21:45,006 INFO [Worker clientId=connect-1, groupId=mirrormaker2-cluster] Cluster ID: UYTj0E0PQOmG9PAb6axowg (org.apache.kafka.clients.Metadata) [DistributedHerder-connect-1]
2020-06-19 05:21:45,008 ERROR [Worker clientId=connect-1, groupId=mirrormaker2-cluster] Uncaught exception in herder work thread, exiting:  (org.apache.kafka.connect.runtime.distributed.DistributedHerder) [DistributedHerder-connect-1]
org.apache.kafka.common.errors.GroupAuthorizationException: Not authorized to access group: mirrormaker2-cluster

This group is something which is internally created/used by the MirrorMaker and I am not sure how do we give the auth permission as my MM CR looks as shown.

apiVersion: kafka.strimzi.io/v1alpha1
kind: KafkaMirrorMaker2
metadata:
  name: brcm-mirror-maker2
spec:
  version: 2.4.0
  replicas: 1
  connectCluster: "mm-backup-cluster"
  clusters:
  - alias: "mm-src-cluster"
    authentication:
      certificateAndKey:
        certificate: user.crt
        key: user.key
        secretName: mm-consumer-user
      type: tls
    bootstrapServers: mm-src-cluster-kafka-bootstrap.kafka-mirror-src.svc:9093
    tls:
      trustedCertificates:
      - certificate: ca.crt
        secretName: mm-src-cluster-cluster-ca-cert
  - alias: "mm-backup-cluster"
    authentication:
      certificateAndKey:
        certificate: user.crt
        key: user.key
        secretName: mm-producer-user
      type: tls
    bootstrapServers: mm-backup-cluster-kafka-bootstrap.kafka-mirror.svc:9093
    config:
      config.storage.replication.factor: 1
      offset.storage.replication.factor: 1
      status.storage.replication.factor: 1
      offset.storage.topic: mm-backup-cluster-offsets
      config.storage.topic: mm-backup-cluster-configs
      status.storage.topic: mm-backup-cluster-status

    tls:
      trustedCertificates:
      - certificate: ca.crt
        secretName: mm-backup-cluster-cluster-ca-cert
  mirrors:
  - sourceCluster: "mm-src-cluster"
    targetCluster: "mm-backup-cluster"
    sourceConnector:
      config:
        replication.factor: 1
        offset-syncs.topic.replication.factor: 1
        sync.topic.acls.enabled: "false"
        offset.storage.topic: mirrormaker2-cluster-offsets
        config.storage.topic: mirrormaker2-cluster-configs
        status.storage.topic: mirrormaker2-cluster-status

    heartbeatConnector:
      config:
        heartbeats.topic.replication.factor: 1
    checkpointConnector:
      config:
        checkpoints.topic.replication.factor: 1
    topicsPattern: ".*"
    groupsPattern: ".*"

Help on this is much appreciated.

Wishes,
Viswanadh.

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and any disclosure, copying, or distribution of this message, or the taking of any action based on it, by you is strictly prohibited.

Deloitte refers to a Deloitte member firm, one of its related entities, or Deloitte Touche Tohmatsu Limited ("DTTL"). Each Deloitte member firm is a separate legal entity and a member of DTTL. DTTL does not provide services to clients. Please see www.deloitte.com/about to learn more.

v.E.1