[
https://issues.apache.org/jira/browse/KAFKA-14061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guram Savinov updated KAFKA-14061:
----------------------------------
Description:
I run mm2 in dedicated mode (not in Kafka Connect).
It's possible to replicate from source to the target cluster without creating
any internal topics on the source cluster. Thanks to KIP-716:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-716%3A+Allow+configuring+the+location+of+the+offset-syncs+topic+with+MirrorMaker2]
But it's impossible to use mm2 for bi-directional replication in case when mm2
has no ACLs to create internal topics on one of two clusters.
I want to replicate data between our Kafka cluster and many others, like a
network hub.
I have ACLs to create internal topics only on my own cluster, but not others.
My proposal is to add configuration which allows to store all the internal
topics of all clusters (heartbeats, checkpoints, configs, statuses, offsets)
in one single Kafka cluster.
was:
It's possible to replicate from source to the target cluster without creating
any internal topics on the source cluster. Thanks to KIP-716:
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-716%3A+Allow+configuring+the+location+of+the+offset-syncs+topic+with+MirrorMaker2]
But it's impossible to use mm2 for bi-directional replication in case when mm2
has no ACLs to create internal topics on one of two clusters.
I want to replicate data between our Kafka cluster and many others, like a
network hub.
I have ACLs to create internal topics only on my own cluster, but not others.
My proposal is to add configuration which allows to store all the internal
topics of all clusters (heartbeats, checkpoints, configs, statuses, offsets)
in one single Kafka cluster.
> mirror-maker2: ability to store internal topics in one single Kafka cluster
> ---------------------------------------------------------------------------
>
> Key: KAFKA-14061
> URL: https://issues.apache.org/jira/browse/KAFKA-14061
> Project: Kafka
> Issue Type: Improvement
> Reporter: Guram Savinov
> Priority: Major
> Labels: ACLs, mirror-maker
>
> I run mm2 in dedicated mode (not in Kafka Connect).
> It's possible to replicate from source to the target cluster without creating
> any internal topics on the source cluster. Thanks to KIP-716:
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-716%3A+Allow+configuring+the+location+of+the+offset-syncs+topic+with+MirrorMaker2]
> But it's impossible to use mm2 for bi-directional replication in case when
> mm2 has no ACLs to create internal topics on one of two clusters.
> I want to replicate data between our Kafka cluster and many others, like a
> network hub.
> I have ACLs to create internal topics only on my own cluster, but not others.
> My proposal is to add configuration which allows to store all the internal
> topics of all clusters (heartbeats, checkpoints, configs, statuses, offsets)
> in one single Kafka cluster.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
