Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
23.02.3
-
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)
Description
Hi There,
We've observed the GTID value within current_gtid.txt is behind what is reported by the maxctrl CLI. We have three Maxscale instances, the current_gtid.txt on each one exhibits the same behaviour. The value within the current_gtid.txt files is at least a day old, yet the binary logs are purged after 3 hrs.
Thanks.
Attachments
Issue Links
- relates to
-
MXS-4785 KafkaCDC JSON conversion is taking most of the CPU time
- Closed