[
https://issues.apache.org/jira/browse/KAFKA-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144388#comment-17144388
]
Ning Zhang commented on KAFKA-9076:
-----------------------------------
[~rhauch] It is true that this jira is not a blocking factor to 2.6.0 release
and thank you for checking it.
Given the PR has been proposed for over 6 months, some users are testing it in
different use cases, I would hope the committers ([~mimaison]) and other
reviewers may take an other review on https://github.com/apache/kafka/pull/7577
and see if we could iterate faster, so that it can formally be part of Kafka in
the 2.7.0 release.
> 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
> Assignee: Ning Zhang
> Priority: Major
> Labels: mirrormaker, pull-request-available
> Fix For: 2.7.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.
> KIP:
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-545%3A+support+automated+consumer+offset+sync+across+clusters+in+MM+2.0
> [https://github.com/apache/kafka/pull/7577]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
