[
https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932616#comment-16932616
]
Qihong Chen commented on KAFKA-7500:
------------------------------------
Hi [~ryannedolan], Thanks for your quick response (y)(y)(y)
Now I know what "primary" means. According to blog [A look inside Kafka
MirrorMaker2|https://blog.cloudera.com/a-look-inside-kafka-mirrormaker-2/] by
Renu Tewari,
{quote}In MM2 only one connect cluster is needed for all the cross-cluster
replications between a pair of datacenters. Now if we simply take a Kafka
source and sink connector and deploy them in tandem to do replication, the data
would need to hop through an intermediate Kafka cluster. MM2 avoids this
unnecessary data copying by a direct passthrough from source to sink.
{quote}
This is exactly what I want! Do you have release schedule for *SinkConnector*,
and *direct passthrough from source to sink* feature?
> 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)
