[jira] [Commented] (KAFKA-13659) MM2 should read all offset syncs at start up

["Chris Egerton (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686112#comment-17686112 ] 

Chris Egerton commented on KAFKA-13659:
---------------------------------------

[~dorwi] thanks for filing this issue. I've removed part of the description that refers to syncing consumer offsets on the downstream cluster with offsets beyond the end of the log, since that's already captured with KAFKA-12468 and a corresponding [PR for that issue|https://github.com/apache/kafka/pull/13178].

 

The remaining part of this ticket is still worth pursuing, and I'd be interested in seeing if we can merge a fix for it. Are you still interested in pursuing this ticket, or would it be okay to reassign to someone else?

> MM2 should read all offset syncs at start up
> --------------------------------------------
>
>                 Key: KAFKA-13659
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13659
>             Project: Kafka
>          Issue Type: Improvement
>          Components: mirrormaker
>            Reporter: Kanalas Vidor
>            Assignee: Kanalas Vidor
>            Priority: Major
>
> MirrorCheckpointTask uses OffsetSyncStore, and does not check whether OffsetSyncStore managed to read to the "end" of the offset-syncs topic. OffsetSyncStore should fetch the endoffset of the topic at startup, and set a flag when it finally reaches the endoffset in consumption. MirrorCheckpointTask.poll should wait for this flag to be true before doing any in-memory updates and group offset management.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)