Comments - MariaDB GTID replication Fix

1 week, 4 days ago Kristian Nielsen

The recommended method is to use CHANGE MASTER TO Master_use_gtid=slave_pos

If you completely rebuilt the Server B then it starts without binlogs, and you may need to reset the Server A replication position. Depending on how you rebuilt the Server B, you may need to SET GLOBAL gtid_slave_pos='xxx' on Server A, or you may be able to use the Master_demote_to_slave=1 option of CHANGE MASTER.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.