Strimzi KafkaMirrorMaker2 - src not able to connect to target cluster (src & target clusters on GKE) #8135
Replies: 1 comment · 8 replies
-
Well, you enabled the ACL rules synchronization. In that case, you have to use ACLs. So you either need to disable it in the MM2 custom resource or add it to your Kafka clusters. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@scholzj - i was able to resolve this issue by setting sync.topic.acls.enabled: "false" in the KafkaMirrorMaker2 yaml however, the MirrorMaker is not yet transferring data from the source to target clusters. Here are the yamls & the logs: KafkaMirrorMaker2 yaml:
Pls note : I'm using the loadbalancer IP for the source & Any ideas why ? Logs from the mirrormaker service:
This does not seem to be showing any outstanding messages, and the messages I'm pushing into the source cluster (using kafka command-line) are not showing up in the target. Pls advise on what needs to be done to fix this ? tia ! |
Beta Was this translation helpful? Give feedback.
All reactions
-
Another observation -- In the topic 'mirrormaker2-cluster-status', i see many tasks the status of which are shown below : many have status - 'RUNNING' some have status - 'UNASSIGNED' |
Beta Was this translation helpful? Give feedback.
All reactions
-
This is something you added to the Mirror Maker 2 custom resource: Or you can of course disable the ACL sync again as we have it by default. |
Beta Was this translation helpful? Give feedback.
All reactions
-
@scholzj - yes, i was able to get past the acl sync issue Any ideas why the mirrormaker is not working as expected ? i.e. it is not transferring data from source to destination .. the logs (pasted above) don't show any errors ! |
Beta Was this translation helpful? Give feedback.
All reactions
-
I'm not sure I understand what the other issue is as it is confusing what is related to the ACLs and what is not. Maybe you should strt form the beginning about what is the current issue. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello All - I'm trying to setup KafkaMirrorMaker2 on Strimzi kafka (on GKE), and it is not working. Currently, i've setup 2 clusters without SSL and authorization enabled.
src cluster -> versa-kafka-gke-w target cluster -> versa-kafka-gke-e
The kafkamirrormaker2 is deployed in src cluster (i,e. versa-kafka-gke-w) also Kafka version is 3.0.0
Here is the kafka-deployment.yaml (same yaml is used in both the clusters, the name is changed per cluster)
Here is the KafkaMirrorMaker2 yaml:
Error i see when i check the logs :
I think this is expected, since the target bootstrap server - versa-kafka-gke-e-kafka-bootstrap uses a ClusterIP, so it should not be accessible from the source cluster i.e. versa-kafka-gke-w
I tried changing the target bootstrap server to -> 'loadbalancer-IP':9094, and i get error, pls see logs below :
From the error, it is clear that KafkaMirrorMaker2 is unable to access the target loadbalancer_IP:9094.
Few questions on the KafkaMirrorMaker2 setup :
What do i need to ensure that the target kafka cluster bootstrap server is accessible ?
tia!
Beta Was this translation helpful? Give feedback.
All reactions