Hi Team
We have configured KafkaMirrorMaker2 as shown below.
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
While launching it with kubectl create it is throwing an error related to topic
authorization... Please let us know if there is any miss in the configuration
or what is that wrong we are doing. My concern is from where this topic is
coming from and how do we give auth permission to it.
org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized to
access topics: [mirrormaker2-cluster-offsets]
2020-05-29 10:49:39,831 INFO [Consumer
clientId=consumer-mirrormaker2-cluster-1, groupId=mirrormaker2-cluster] Cluster
ID: UYTj0E0PQOmG9PAb6axowg (org.apache.kafka.clients.Metadata)
[DistributedHerder-connect-1]
2020-05-29 10:49:39,833 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.TopicAuthorizationException: Not authorized to
access topics: [mirrormaker2-cluster-offsets]
2020-05-29 10:49:39,848 INFO Stopped
http_8083@2f3c6ac4{HTTP/1.1,[http/1.1]}{0.0.0.0:8083}
(org.eclipse.jetty.server.AbstractConnector) [Thread-1]
2020-05-29 10:49:39,849 INFO node0 Stopped scavenging
(org.eclipse.jetty.server.session) [Thread-1]
2020-05-29 10:49:40,177 INFO Started
o.e.j.s.ServletContextHandler@1280851e{/,null,AVAILABLE}
(org.eclipse.jetty.server.handler.ContextHandler) [main]
2020-05-29 10:49:40,177 INFO REST resources initialized; server is started and
ready to handle requests (org.apache.kafka.connect.runtime.rest.RestServer)
[main]
2020-05-29 10:49:40,177 INFO Kafka Connect started
(org.apache.kafka.connect.runtime.Connect) [main]
2020-05-29 10:49:40,177 INFO Kafka Connect stopping
(org.apache.kafka.connect.runtime.Connect) [Thread-10]
2020-05-29 10:49:40,177 INFO Stopping REST server
(org.apache.kafka.connect.runtime.rest.RestServer) [Thread-10]
2020-05-29 10:49:40,178 INFO REST server stopped
(org.apache.kafka.connect.runtime.rest.RestServer) [Thread-10]
2020-05-29 10:49:40,178 INFO [Worker clientId=connect-1,
groupId=mirrormaker2-cluster] Herder stopping
(org.apache.kafka.connect.runtime.distributed.DistributedHerder) [Thread-10]
2020-05-29 10:49:45,179 INFO [Worker clientId=connect-1,
groupId=mirrormaker2-cluster] Herder stopped
(org.apache.kafka.connect.runtime.distributed.DistributedHerder) [Thread-10]
2020-05-29 10:49:45,179 INFO Kafka Connect stopped
(org.apache.kafka.connect.runtime.Connect) [Thread-10]
Need help to resolve this.
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
