Ravindranath Kakarla created KAFKA-15262:
--------------------------------------------
Summary: MirrorHeartbeatConnector is not working as documented
Key: KAFKA-15262
URL: https://issues.apache.org/jira/browse/KAFKA-15262
Project: Kafka
Issue Type: Bug
Components: mirrormaker
Affects Versions: 3.5.0, 3.4.0, 2.8.0
Reporter: Ravindranath Kakarla
As per the MM2
[KIP-382|[https://cwiki.apache.org/confluence/display/KAFKA/KIP-382%3A+MirrorMaker+2.0],]
the MirrorHeartbeatConnector should emit pings to heartbeat topic on the
source cluster which then gets replicated to the target cluster. This can be
used to demonstrate that MM2 is replicating the data.
"""
h2. Internal Topics
MM2 emits a *heartbeat* *topic* in each source cluster, which is replicated to
demonstrate connectivity through the connectors. Downstream consumers can use
this topic to verify that a) the connector is running and b) the corresponding
source cluster is available. Heartbeats will get propagated by source and sink
connectors s.t. chains like backup.us-west.us-east.heartbeat are possible.
"""
However, this is not happening right now. To contrary, the
MirrorHeartbeatConnector is producing heartbeat pings to target cluster instead
of source. This is not much useful as it won't help detect problems connecting
to source cluster or with the data replication.
Is my understanding of the MirrorHeartbeatConnector accurate?
[Code
Ref|https://github.com/apache/kafka/blob/ed44bcd71b3b9926c474033882eaa6c1cf35cfa4/connect/mirror/src/main/java/org/apache/kafka/connect/mirror/MirrorHeartbeatTask.java#L65]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
