Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-09-15 Thread Manoj.Agrawal2
Hi Ryanne/Josh, I'm working on active-active mirror maker and while translating consumer offset from source- cluster A to dest cluster B. any pointer would be helpful . Cluster A Cluster Name--A Topic name: testA Consumer group name: mm-testA-consumer Cluster -B Cluster Name--B Topic name: sou

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-21 Thread Ryanne Dolan
Josh, make sure there is a consumer in cluster B subscribed to A.topic1. Wait a few seconds for a checkpoint to appear upstream on cluster A, and then translateOffsets() will give you the correct offsets. By default MM2 will block consumers that look like kafka-console-cosumer, so make sure you sp

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-20 Thread Josh C
Thanks again Ryanne, I didn't realize that MM2 would handle that. However, I'm unable to mirror the remote topic back to the source cluster by adding it to the topic whitelist. I've also tried to update the topic blacklist and remove ".*\.replica" (since the blacklists take precedence over the whi

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-19 Thread Ryanne Dolan
Josh, if you have two clusters with bidirectional replication, you only get two copies of each record. MM2 won't replicate the data "upstream", cuz it knows it's already there. In particular, MM2 knows not to create topics like B.A.topic1 on cluster A, as this would be an unnecessary cycle. > is

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-19 Thread Josh C
Sorry, correction -- I am realizing now it would be 3 copies of the same topic data as A.topic1 has different data than B.topic1. However, that would still be 3 copies as opposed to just 2 with something like topic1 and A.topic1. As well, if I were to explicitly replicate the remote topic back to

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-19 Thread Josh C
Thanks for the clarification Ryanne. In the context of active/active clusters, does this mean there would be 6 copies of the same topic data? A topics: - topic1 - B.topic1 - B.A.topic1 B topics: - topic1 - A.topic1 - A.B.topic1 Out of curiosity, is there a reason for MM2 not emitting checkpoint

Re: MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-19 Thread Ryanne Dolan
Josh, yes it's possible to migrate the consumer group back to the source topic, but you need to explicitly replicate the remote topic back to the source cluster -- otherwise no checkpoints will flow "upstream": A->B.topics=test1 B->A.topics=A.test1 After the first checkpoint is emitted upstream,

MirrorMaker 2.0 - Translating offsets for remote topics and consumer groups

2020-08-18 Thread Josh C
Hi there, I'm currently exploring MM2 and having some trouble with the RemoteClusterUtils.translateOffsets() method. I have been successful in migrating a consumer group from the source cluster to the target cluster, but was wondering how I could migrate this consumer group back to the original so