...

Discussion thread: here

JIRA: here

Motivation

MirrorMaker 2 uses AdminClient  directly to create topics and sync configurations like topic configs and ACLs by enabling sync.topic.configs.enabled  and sync.topic.acls.enabled , while this approach simplifies the resource management for MM2, it does create the following problems for users who have their systems or tooling to manage Kafka resources:

1. External Kafka resource management tool/system may override the same configurations that MM2 synced previously. 
2. Create/Modify resources using AdminClient directly lead to a lack of auditing and tracing resources.

In use-cases where users have their own centralized system to manage Kafka topics and ACLs, they should easily integrate MirrorMaker2 with their internal ecosystem. 

Currently, there are a couple of options to deal with these problems, 

1. Drop mirrored topics from a centralized system and accept the risk of not tracing these topics. This direction will avoid conflict between topics monitored by MM2 and the centralized system for resource management.
2. Creating topics up-front and disabling features like sync.topic.configs.enabled , sync.topic.acls.enabled.

The current approach also assumes that the user running MM2 has the Admin right to create topics, which is only valid if the user who runs MM2 also manages both source and destination clusters. 

This KIP proposes a way for users to run MM2 with custom implementation for the Kafka resource manager. 

Public Interfaces

The KIP proposes adding a new interface called KafkaResourceManager that defines how MM2 will create, modify, and list any Kafka topics and ACLs. MirrorMaker2’s original behaviour will be kept in DefaultResourceManager.

...