[MXS-4764] KafkaCDC: Option to use the latest GTID Created: 2023-09-16  Updated: 2023-10-16  Resolved: 2023-10-16

Status: Closed
Project: MariaDB MaxScale
Component/s: kafkacdc
Affects Version/s: 23.02.3, 23.08.0
Fix Version/s: 24.02.0

Type: New Feature Priority: Major
Reporter: Presnickety Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: replication
Environment:

RHEL v8.2
VMware vCenter v7
MariaDB v10.7 (3 node Galera cluster)
Maxcsale v23.02.3 (one instance of each per MariaDB VM for redundancy)

Sprint: MXS-SPRINT-192

 Description   

We see a lot of the following errors messages especially after failover events. We resolve this by manually setting the 'gtid' parameter in the KafkaCDC configuration then restarting the load balancers;

2023-09-02 11:13:25 error : Failed to read replicated event: 1236, Could not find GTID state requested by slave in any binlog files. Probably the slave state is too old and required binlog files have been purged.

 Comments   
Comment by Presnickety [ 2023-09-16 ]

Please provide an option for the gtid parameter so that it can automatically grab the latest cluster GTID if required e.g. 'gtid=latest'.

Thanks.

Generated at Thu Feb 08 04:30:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.