Hello, Thank you very much for your suggestions and assistance. I have tried your second method and successfully used `producer.override.bootstrap.servers` as the key, achieving the desired effect. I appreciate your warm response and valuable time. Thanks again!
Best regards, On Tue, Feb 27, 2024 at 11:55 PM Ryanne Dolan <ryannedo...@gmail.com> wrote: > Hello, the heartbeat connector is a sink connector, so it normally would > write to the target cluster. I can think of two ways to achieve what you > want: > > 1) set up a second connect cluster that sinks to the source cluster, and > run just the heartbeat connector there. > > 2) override the heartbeat connector's producer configuration to point to > the source cluster. I forget the exact spelling, but something like > `producer.bootstrap.servers` etc might work. > > Ryanne > > On Tue, Feb 27, 2024, 8:51 AM aaron ai <aaro...@apache.org> wrote: > > > Dear Kafka Community, > > > > I am reaching out for some guidance regarding an issue I've encountered > > while setting up Kafka MirrorMaker2 (MM2) for data synchronization from a > > source cluster (A) to a target cluster (B). > > > > During my setup with MM2 on dedicated mode, I observed that the heartbeat > > topic is established on the source cluster, and the messages within the > > heartbeat are being synchronized to the target cluster as expected. > > However, when configuring MM2 on Kafka Connect using the > > connect-distributed.properties file, it appears that I can only set the > > bootstrap.servers to point to the endpoints of the target cluster B. > > Consequently, when I manually establish the MirrorHeartbeatConnector, the > > heartbeat topic also gets created on the target cluster instead of the > > source. > > > > This leads me to wonder if this behavior is expected or if I might be > > missing a step in the configuration process. My goal is to have the > > heartbeat topic created on the source cluster. Could you please advise on > > whether this is possible and, if so, how it can be achieved? Are there > > specific configurations or steps that I should follow to ensure the > > heartbeat topic is correctly established on the source cluster? > > > > I appreciate any insights or recommendations you might have on this > matter. > > > > Best regards, > > >
