Hi Massimiliano, A small amount of re-delivery is expected when using MirrorMaker2 3.5+ offsets replication. This is because MM2 does not offer exactly once offset replication.
I gave a conference talk recently about this which you may find informative: https://current.confluent.io/2024-sessions/mirrormaker-2s-offset-translation-isnt-exactly-once-and-thats-okay You can also read about this here, and in the linked tickets: https://issues.apache.org/jira/browse/KAFKA-12468 Thanks, Greg On Fri, Oct 4, 2024 at 1:31 PM Massimiliano Rotondo <scuta1...@gmail.com> wrote: > Hello, > > I'm experiencing a side bug with usage of Kafka MirrorMaker2, all is > described in the below post: > > > https://stackoverflow.com/questions/79051730/kafka-mirrormaker2-stop-offset-sync-when-consumer-group-idle-on-source-cluster > > The same "bug" has been reproduced using updated Kafka Cluster 3.7.1 on > both source/destination (so it seems not depending on the old version of > the source cluster). > > Could you please support with this? > > Best Regards, > > Massimiliano Rotondo >
