How to resolve GTID difference between Master and Slave servers in MariaDB replication using MaxScale?

Question

I wrote accidently directly on the Slave DB, and therefore the data is not in sync anymore.

When I check MaxScale status, all servers are running, but the Slaves are not detected as "Slave" and there is a difference in GTID.

Does anyone know how to put them back in sync?

I've already searched for information into the documentation of MaxScale, but I could not find this specific usecase there: https://mariadb.com/kb/en/mariadb-maxscale-2302-automatic-failover-with-mariadb-monitor/

Answer 1

I have found the solution in this article: https://www.redips.net/mysql/replication-slave-relay-log-corrupted/

I had to detect the last bin log from the Master node, and to execute the following commands on both slave nodes:

SHOW SLAVE STATUS \G;
STOP SLAVE;
RESET SLAVE;
CHANGE MASTER TO master_log_file='nodex-bin.XXX(last binlog by date)',
 master_log_pos=4; # 4 for the beginning of the log file
START SLAVE;