Switching from MariaDB to Percona - what are the pitfalls?

Question

MySQL

Hello! We use MariaDB Master-Slave (InnoDB database engine). We plan to switch to Percona Galera Cluster (the engine will remain InnoDB). Will it be necessary to make changes to the database structure? Now the Percona infrastructure (2 nodes + arbitrator) is already deployed, load tests (simulating real requests coming to the database) are running fine, but maybe there are pitfalls that you should pay attention to?

Answer 1

I am running zabbix on mysql fork - percona. The purpose of the transition was an attempt to optimize the operation of the DBMS when moving storage to SSD, it is precisely for this purpose. There were no additional features when translating database objects.

Answer 2

Note that in a master-master configuration, transactions are atomic within 1 server.

Answer 3

We encountered random garbage in text/binary type fields in MEMORY tables. The tables were filled in something like this (I don’t remember the exact request, it was a long time ago): In the text fields, instead of the expected meaningful lines, there was some garbage. The error appeared every other time, and the admin was actively doing something on the server, trying to increase performance. It was not possible to achieve unambiguous reproduction (and create a ticket).

Answer 4

Do not arrange replication from maria to percona and everything will be fine.