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

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.1.0, 3.2.0
Component/s: mirrormaker
Labels:
None

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:

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