[
https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878214#comment-16878214
]
Srikala commented on KAFKA-7500:
--------------------------------
[~ryannedolan], Thanks for all your efforts on MM2. I am also eagerly
looking forward MM2 to be on 2.4.0.
Appreciate your input on the following scenario:
I have setup two clusters K1 and K2 and configured MM2 replication for TOPIC1.
My consumer group is "TOPIC_GROUP".
1. To start with K1 cluster is active and "TOPIC_GROUP" is actively consuming
TOPIC1 from K1.
2. Now, the failover to K2 is triggered and the "TOPIC_GROUP" starts consuming
from K2. I have used RemoteClusterUtils.translateOffsets to seek to the correct
offset for K1.TOPIC1.
3. During failover, there were #N messages in TOPIC1 in K1 that were not
consumed by "TOPIC_GROUP" but were replicated in K2 and consumed by
"TOPIC_GROUP" in K2 as K1.TOPIC1
In this scenario per my testing, when K1 comes back online and TOPIC_GROUP
restarts consuming from K1, the #N messages will be consumed again from TOPIC1.
Is this expected? Is there a way to do consumer.seek on the TOPIC1 partitions
in K1, based on the K1.TOPIC1 consumer offsets in K2?
Thanks!
> MirrorMaker 2.0 (KIP-382)
> -------------------------
>
> Key: KAFKA-7500
> URL: https://issues.apache.org/jira/browse/KAFKA-7500
> Project: Kafka
> Issue Type: New Feature
> Components: KafkaConnect, mirrormaker
> Reporter: Ryanne Dolan
> Priority: Minor
> Fix For: 2.4.0
>
>
> Implement a drop-in replacement for MirrorMaker leveraging the Connect
> framework.
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0]
> [https://github.com/apache/kafka/pull/6295]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
