[
https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16878308#comment-16878308
]
Ryanne Dolan commented on KAFKA-7500:
-------------------------------------
[~Munamala] Yes, the translateOffsets() works both ways. When K1 comes back
online, you can "failback" from K2 to K1 once a checkpoint for TOPIC_GROUP is
emitted upstream to K1. The checkpoint will have offsets for TOPIC1 on K1
(translated from K1.TOPIC1 on K2). You can then seek() to skip over the records
TOPIC_GROUP already consumed in K2.
The tricky part here is that you need to make sure MM2 is configured to emit
checkpoints both from K1->K2 and K2->K1. Configure the whitelists like:
K1->K2.topics = TOPIC1, K2.TOPIC1
K2->K1.topics = TOPIC1, K1.TOPIC1
K1->K2.groups = TOPIC_GROUP
K2->K1.groups = TOPIC_GROUP
Otherwise, you won't see checkpoints for TOPIC1 going from K2 to K1.
Ryanne
> 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)
