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 data for the source topic AND the remote topic as a pair as opposed to having to explicitly replicate the remote topic back to the source cluster just to have the checkpoints emitted upstream? Josh On Wed, Aug 19, 2020 at 6:16 AM Ryanne Dolan <ryannedo...@gmail.com> wrote: > 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, > RemoteClusterUtils.translateOffsets() will translate B's A.test1 offsets > into A's test1 offsets for you. > > Ryanne > > On Tue, Aug 18, 2020 at 5:56 PM Josh C <josh.fl.c...@gmail.com> wrote: > > > 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 source topic? > > > > It is my understanding that there isn't any checkpoint data being > > emitted for this consumer group since it is consuming from a mirrored > topic > > in the target cluster. I'm currently getting an empty map since there > isn't > > any checkpoint data for 'target.checkpoints.internal' in the source > > cluster. So, I was wondering how would I get these new translated offsets > > to migrate the consumer group back to the source cluster? > > > > Please let me know if my question was unclear or if you require further > > clarification! Appreciate the help. > > > > Thanks, > > Josh > > >
