[ https://issues.apache.org/jira/browse/KAFKA-13562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Harris resolved KAFKA-13562. --------------------------------- Fix Version/s: 3.3.3 3.4.1 3.5.0 Resolution: Fixed > Mirror Maker 2 Negative Offsets > ------------------------------- > > Key: KAFKA-13562 > URL: https://issues.apache.org/jira/browse/KAFKA-13562 > Project: Kafka > Issue Type: Bug > Components: KafkaConnect, mirrormaker > Affects Versions: 2.8.1 > Reporter: David Urton > Priority: Minor > Fix For: 3.3.3, 3.4.1, 3.5.0 > > > We recently started a migration from a traditional self-managed Apache Kafka > cluster to Strimzi. We enabled group offset sync and something I'm struggling > to fully understand is why the mirrored group has a current-offset matching > (or close to matching) the source offset, but then the log-end-offset > essentially starts over resulting in a negative lag. Is this just aesthetic? > The lag is slowly moving closer to 0 but some of our negative lags are very > "large". Several hundred million. I verified all the data has moved over, but > I'm struggling on this lag issue. > Any help clearing this up is much appreciated! > Source cluster is 2.4.1 destination is 2.8.1. Detailed info in the Github URL. -- This message was sent by Atlassian Jira (v8.20.10#820010)