Debezium MySQL connector - Kafka restart triggers Binlog dump

[Omar Ghalawinji]

Hello,

I am using Debezium MySQL connector 1.6 on a cloud managed Kafka service.

I noticed that every time the kafka service is restarted (post a maintenance operation for example), the connector triggers a Binlog dump GTID in the DB server.

This is causing pics in the memory usage and temporarily affecting the performance of the DB. (screenshots below)

The restart of the managed kafka service doesn't force the connector to do a snapshot. I checked the logs and it shows the connector continues streaming from the last recorded binlog location normally.

Do you have an idea why this happens and how to avoid it?

Many thanks

[Gunnar Morling]

Hi,

What exactly is "Binlog dump GTID"? Do you observe the same when restarting the connector? I can't see how a restart of Kafka would trigger any such activity. Hard to tell anything more meaningful without knowing more details.

--Gunnar