In this case the consumers just subscribe to "topic1" like normal, and the remote topics (primary.topic1, secondary.topic1) are just for DR. MM2 is not required for things to work under normal circumstances, but if one cluster goes down you can recover its data from the other.
Ryanne On Thu, Jan 16, 2020, 2:35 AM dixingxing <dixingxin...@163.com> wrote: > hello everyone: > > I've read this slide recently( > https://www.confluent.io/kafka-summit-lon19/disaster-recovery-with-mirrormaker-2-0/), > i'm not sure how to deploy active-active clusters like this. > > > There is no detail about how to make an "Effectively one big consumer > group", since there is MM2 between the two clusters, so the topic should > like this: > *primary cluster:* > topic1 > secondary.topic1 > > *secondary cluster:* > topic1 > primary.topic1 > > I think the simplest way to make an "Effectively one big consumer group" > is : > Each client should make 2 cosumer instances, one subscribe > primary.topic1, and the other subscribe secondary.topic1, so if one cluster > crash down, LB just need to failover to another cluster, the consumer > should do nothing, every thing will works fine. > But it seems there is no need for MM2, or MM2 is just for disaster > recovery? > Am i misunderstanding about this slide? > > > > > > > > > > > >
