[jira] [Commented] (KAFKA-7500) MirrorMaker 2.0 (KIP-382)

["zhongyushuo (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081735#comment-17081735 ] 

zhongyushuo commented on KAFKA-7500:
------------------------------------

Hi [~ryannedolan], Thanks for your great job.
I have a question about the failover in the scenario Srikala described. 
Let's say that we have two clusters K1 and K2 and configured MM2 replication for TOPIC1. The consumer group is "TOPIC_GROUP".
We configured the whitelist as you saied:
K1->K2.topics = TOPIC1, K2.TOPIC1
K2->K1.topics = TOPIC1, K1.TOPIC1
K1->K2.groups = TOPIC_GROUP
K2->K1.groups = TOPIC_GROUP
In the beginning the conusmers consume Topic1 from K1. Then K1 out of service, failover happens. Consumers start to consume K1.TOPIC1 from K2.
And producers switch to producing records to K1.TOPIC1 on K2 cluster. The record will sync from K2 to K1 now. The question is that which target topic the records will be sync to on K1 cluser? TOPIC1 or K2.K1.TOPIC1? 

> 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: Ryanne Dolan
>            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)