[
https://issues.apache.org/jira/browse/KAFKA-15172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742994#comment-17742994
]
hudeqi commented on KAFKA-15172:
--------------------------------
Hi,[~mimaison] [~ChrisEgerton] I am currently doing the work of using MM2 to
realize the disaster recovery of active and standby clusters, and it has been
applied to the production environment, so I am still very interested in this
issue. I don’t know if it can be assigned to me (if it is not suitable, you can
always reassign).
For this problem, I think it should not only be synchronized with Topic write
Acl, but also synchronized with Group Acl or even user scram credential, right?
I can initiate a KIP if this is confirmed, thanks!
> Allow exact mirroring of ACLs between clusters
> ----------------------------------------------
>
> Key: KAFKA-15172
> URL: https://issues.apache.org/jira/browse/KAFKA-15172
> Project: Kafka
> Issue Type: Task
> Components: mirrormaker
> Reporter: Mickael Maison
> Assignee: hudeqi
> Priority: Major
> Labels: needs-kip
>
> When mirroring ACLs, MirrorMaker downgrades allow ALL ACLs to allow READ. The
> rationale to is prevent other clients to produce to remote topics.
> However in disaster recovery scenarios, where the target cluster is not used
> and just a "hot standby", it would be preferable to have exactly the same
> ACLs on both clusters to speed up failover.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
