[
https://issues.apache.org/jira/browse/KAFKA-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957563#comment-16957563
]
Ryanne Dolan commented on KAFKA-9076:
-------------------------------------
[~yangguo1220] I took a look at the PR. Very cool! I see that you only sync
offsets for consumers that are inactive and behind the checkpoint, which makes
a lot of sense. This seems to allay my concerns above.
I'm glad to hear this is working for you internally. I'm onboard, but you'll
need a small KIP to make these changes, since the public API is affected.
> MirrorMaker 2.0 automated consumer offset sync
> ----------------------------------------------
>
> Key: KAFKA-9076
> URL: https://issues.apache.org/jira/browse/KAFKA-9076
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker
> Affects Versions: 2.4.0
> Reporter: Ning Zhang
> Priority: Major
> Labels: mirrormaker, pull-request-available
> Fix For: 2.5.0
>
>
> To calculate the translated consumer offset in the target cluster, currently
> `Mirror-client` provides a function called "remoteConsumerOffsets()" that is
> used by "RemoteClusterUtils" for one-time purpose.
> In order to make the consumer and stream applications migrate from source to
> target cluster transparently and conveniently, e.g. in event of source
> cluster failure, a background job is proposed to periodically sync the
> consumer offsets from the source to target cluster, so that when the consumer
> and stream applications switch to the target cluster, it will resume to
> consume from where it left off at source cluster.
>
> https://github.com/apache/kafka/pull/7577
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
