[ https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932658#comment-16932658 ]
Ryanne Dolan commented on KAFKA-7500: ------------------------------------- [~qihong] the direct passthrough described there is what MM2 currently does -- there are dedicated workers consuming from each source cluster and writing to each target cluster, without requiring a bunch of Connect clusters, and without requiring hops through an intermediate Kafka cluster. I think the confusion here is that "sink" does not imply "SinkConnector". Sink in this context is the target cluster. > MirrorMaker 2.0 (KIP-382) > ------------------------- > > Key: KAFKA-7500 > URL: https://issues.apache.org/jira/browse/KAFKA-7500 > Project: Kafka > Issue Type: New Feature > Components: KafkaConnect, mirrormaker > Affects Versions: 2.4.0 > Reporter: Ryanne Dolan > Assignee: Manikumar > Priority: Major > Labels: pull-request-available, ready-to-commit > Fix For: 2.4.0 > > Attachments: Active-Active XDCR setup.png > > > ImplementĀ a drop-in replacement for MirrorMaker leveraging the Connect > framework. > [https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0] > [https://github.com/apache/kafka/pull/6295] -- This message was sent by Atlassian Jira (v8.3.4#803005)