[
https://issues.apache.org/jira/browse/KAFKA-16193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811003#comment-17811003
]
Greg Harris commented on KAFKA-16193:
-------------------------------------
Hi [~filatov_m] I believe this is a supported use-case, if a bit roundabout.
Instead of using the dedicated MirrorMaker driver that controls the placement
of the connectors, you can instead host a single Connect cluster with internal
topics (configs, offsets, source) on your internal Kafka.
You can then configure two sets of source/checkpoint/heartbeat connectors, and
use the producer.override.* settings to direct the output records.
I believe this was also the motivation behind
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-716%3A+Allow+configuring+the+location+of+the+offset-syncs+topic+with+MirrorMaker2]
which controls the placement of the mm2 offset syncs topic.
> Storing mm2 topics on source side
> ---------------------------------
>
> Key: KAFKA-16193
> URL: https://issues.apache.org/jira/browse/KAFKA-16193
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker
> Reporter: Mikhail Filatov
> Priority: Major
>
> We have 2 Kafka clusters and one of them is external. We use Mirror Maker to
> replicate one topic from our Kafka to external one but Mirror Maker also
> creates its service topic on target side (mm2-configs.source.internal,
> mm2-offsets.source.internal, mm2-status.source.internal topics).
> We would like to keep such topics on our source side, but as I understand it
> is not configurable and topics created only on target side -
> [https://github.com/apache/kafka/blob/3.5/connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorMakerConfig.java#L182]
> If we can manage workerConfig and specify the side where such topics to keep,
> it could solve the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
