You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Chetan (Jira)" <ji...@apache.org> on 2022/11/02 06:28:00 UTC
[jira] [Comment Edited] (KAFKA-12635) Mirrormaker 2 offset sync is incorrect if the target partition is empty
[ https://issues.apache.org/jira/browse/KAFKA-12635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627482#comment-17627482 ]
Chetan edited comment on KAFKA-12635 at 11/2/22 6:27 AM:
----------------------------------------------------------
[~fyi] / [~mimaison] I just used the Kafka 3.3.1 release to run mirror-maker(which should have this fix), to mirror from existing cluster to a new cluster and i can still see negative lags for various consumer group. !image-2022-11-02-11-53-33-329.png|width=1067,height=198!
was (Author: JIRAUSER297821):
[~fyi] / [~mimaison] I just used the Kafka 3.3.1 release to run mirror-maker(which should have this fix), to mirror from existing cluster to a new cluster and i can still see negative lags for various consumer group. !image-2022-11-02-11-53-33-329.png|width=1067,height=198!
> Mirrormaker 2 offset sync is incorrect if the target partition is empty
> -----------------------------------------------------------------------
>
> Key: KAFKA-12635
> URL: https://issues.apache.org/jira/browse/KAFKA-12635
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Affects Versions: 2.7.0
> Reporter: Frank Yi
> Assignee: Mickael Maison
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: image-2022-11-02-11-53-33-329.png, image-2022-11-02-11-56-34-994.png, screenshot-1.png
>
>
> This bug occurs when using Mirrormaker with "sync.group.offsets.enabled = true".
> If a source partition is empty, but the source consumer group's offset for that partition is non-zero, then Mirrormaker sets the target consumer group's offset for that partition to the literal, not translated, offset of the source consumer group. This state can be reached if the source consumer group consumed some records that were now deleted (like by a retention policy), or if Mirrormaker replication is set to start at "latest". This bug causes the target consumer group's lag for that partition to be negative and breaks offset sync for that partition until lag is positive.
> The correct behavior when the source partition is empty would be to set the target offset to the translated offset, not literal offset, which in this case would always be 0.
> Original email thread on this issue: https://lists.apache.org/thread.html/r7c54ee5f57227367b911d4abffa72781772d8dd3b72d75eb65ee19f7%40%3Cusers.kafka.apache.org%3E
--
This message was sent by Atlassian Jira
(v8.20.10#820010)