[
https://issues.apache.org/jira/browse/KAFKA-15992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795777#comment-17795777
]
Chris Egerton commented on KAFKA-15992:
---------------------------------------
The heartbeats topic name is already configurable in replication policies as of
[KIP-690|https://cwiki.apache.org/confluence/display/KAFKA/KIP-690%3A+Add+additional+configuration+to+control+MirrorMaker+2+internal+topics+naming+convention].
While it's still an option to augment the {{DefaultReplicationPolicy}} class
with configuration properties to control its heartbeat topic, users can also
subclass the {{DefaultReplicationPolicy}} to add custom logic right now if
they'd like to.
I don't raise these points as reasons to not add this configurability to the
{{DefaultReplicationPolicy}} class, but just to note the current workarounds
that are available in case users need this right now and can't wait for a KIP
to be approved and released.
> Make MM2 heartbeats topic name configurable
> -------------------------------------------
>
> Key: KAFKA-15992
> URL: https://issues.apache.org/jira/browse/KAFKA-15992
> Project: Kafka
> Issue Type: Improvement
> Components: mirrormaker
> Affects Versions: 3.7.0
> Reporter: Viktor Somogyi-Vass
> Assignee: Bertalan Kondrat
> Priority: Major
>
> With DefaultReplicationPolicy, the heartbeats topic name is hard-coded.
> Instead, this should be configurable, so users can avoid collisions with the
> "heartbeats" topics of other systems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
