[
https://issues.apache.org/jira/browse/KAFKA-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825346#comment-16825346
]
Ryanne Dolan commented on KAFKA-7500:
-------------------------------------
[~terence.yi] the most trivial scenario would be something like this:
{{clusters = primary, secondary}}
{{primary.bootstrap.servers = primary1.host:9092, primary2.host:9092,
primary3.host:9092}}
{{secondary.bootstrap.servers = secondary1.host:9092, secondary2.host:9092,
secondary3.host:9092}}
{{primary->secondary.enabled = true}}
{{}}{{secondary->primary.enabled = true}}
{{primary->secondary.topics = .*}}
{{secondary->primary.topics = .*}}
... where there are two clusters replicating each other. Then some simple
things you can test include:
# create a topic on either cluster; a remote topic should show up on the other
# send records to a topic on one cluster and verify the same records appear on
the other
# change a topic's configuration, e.g. retention.policy=compact, and verify
the config is sync'd to the other
# change a topic's ACL and verify the ACL is sync'd to the other
# consume from a topic in one cluster and verify that checkpoints are emitted
for the group to the other
# use RemoteClusterUtils to translate a consumer's offsets from one cluster to
the other and verify no records are skipped
etc
I'm putting together documentation for more advanced scenarios and will share
when ready.
> 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
> Assignee: Ryanne Dolan
> Priority: Minor
>
> Implement a drop-in replacement for MirrorMaker leveraging the Connect
> framework.
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
