'Kafka MirorMaker2 ports for inter cluster communication
I have setup Apache MirrorMaker 3.0.0 with active-active strategy for two Kafka clusters (named DC, DR). So topic on DC is replicated by MirrorMaker2 as DC.<topic_name> on the DR cluster and vice-vera.
In each cluster i have setup 3 kafka broker nodes.
Lets suppose below IP config is used
DC 1st node IP : kafka-dc-server1:9092
DC 2nd node IP : kafka-dc-server2:9092
DC 3rd node IP : kafka-dc-server3:9092
DR 1st node IP : kafka-dr-server1:9092
DR 2nd node IP : kafka-dr-server2:9092
DR 3rd node IP : kafka-dr-server3:9092
Connect-maker properties
DC.bootstrap.servers = kafka-dc-server1:9092, kafka-dc-server2:9092, kafka-dc-server3:9092
DR.bootstrap.servers = kafka-dr-server1:9092, kafka-dr-server2:9092, kafka-dr-server3:9092
Just want to understand whether only 9092 port is sufficient to inter cluster communication(records, offset and other metadata transition) or do we need to open connectivity on some ports also?
Solution 1:[1]
If port 9092 is used as each server.properties > listeners setting, then , yes, those are the bootstrap-server values for any client communication.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | OneCricketeer |