[ https://issues.apache.org/jira/browse/KAFKA-13397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mickael Maison resolved KAFKA-13397. ------------------------------------ Fix Version/s: 3.2.0 Resolution: Fixed > MirrorMaker2 shouldn't mirror Connect's internal topics > ------------------------------------------------------- > > Key: KAFKA-13397 > URL: https://issues.apache.org/jira/browse/KAFKA-13397 > Project: Kafka > Issue Type: Bug > Components: mirrormaker > Reporter: Dongjin Lee > Assignee: Dongjin Lee > Priority: Minor > Fix For: 3.2.0 > > > This issue is a follow-up of KAFKA-10777 > ([KIP-690|https://cwiki.apache.org/confluence/display/KAFKA/KIP-690%3A+Add+additional+configuration+to+control+MirrorMaker+2+internal+topics+naming+convention]). > As of present, a user can set custom 'replication.policy.separator' > configuration in MirrorMaker 2. It determines the topic name of internal > topics like heartbeats, checkpoints, and offset-syncs > ([KIP-690|https://cwiki.apache.org/confluence/display/KAFKA/KIP-690%3A+Add+additional+configuration+to+control+MirrorMaker+2+internal+topics+naming+convention]). > However, there are some glitches here: > # MirrorMaker2 creates internal topics to track the offsets, configs, and > status of the MM2 tasks. But, these topics are not affected by a custom > 'replication.policy.separator' settings - that is, these topics may be > replicated against the user`s intention. > # The internal topic names include a dash in their name (e.g., > 'mm2-offsets.\{source}.internal') so, a single '-' should be disallowed when > configuring 'replication.policy.separator'. -- This message was sent by Atlassian Jira (v8.20.1#820001)