[KAFKA-13397] MirrorMaker2 shouldn't mirror Connect's internal topics

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.1.0, 3.2.0
• Component/s: mirrormaker
• Assignee: Dongjin Lee
• Reporter: Dongjin Lee
• Created: 24/Oct/21 11:21
• Updated: 24/Nov/21 10:35
• Resolved: 17/Nov/21 17:22

Description

This issue is a follow-up of KAFKA-10777 (KIP-690).

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).

However, there are some glitches here:

1. 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.
2. 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'.

Issue Links

• links to: GitHub Pull Request #11431