We're seeing strange behaviour. Mysql connector that is running and successfully producing events on restart starts to fail with error, that binlogs are not available anymore.
The error is correct - some non active gtid positions were indeed purged. But it was during failover already long time ago. So it seems reconnecting hides the real problem until next restart.
After real restart the connector actually checks mysql server values and fails.
org.apache.kafka.connect.errors.ConnectException: The connector is trying to read binlog starting at GTIDs
, but this is no longer available on the server.
But just few hours ago it "succeeded" restoring connection.
And then INFO: Trying to restore lost connection to 10.222.2.102:3306
2020-01-24 03:09:53.685 s2w22l
INFO: Connected to 10.222.2.102:3306 at ac917707-0327-11ea-87a2-fa163e4b55f4:1-7166031,ed5b8fc3-daab-11e8-b102-fa163e4b55f4:1-325053312,ed6c7f2a-daab-11e8-b595-fa163e0684a1:1-38186365 (sid:107400, cid:16595316)
+ succeed and produced all events.
This also indicates that the strict binlog match and failure is not always needed - on restore lost connection flow it actually works.