Changing GTID Mode on Online Servers 8. On each server, execute: 9. On each server, add  gtid_mode=ON  and  enforce_gtid_consistency=ON  to  my.cnf . SET @@GLOBAL.GTID_MODE = ON; You are now guaranteed that all transactions have a GTID (except transactions generated in step 5 or earlier, which have already been processed). To start using the GTID protocol so that you can later perform automatic fail-over, execute the following on each replica. Optionally, if you use multi-source replication, do this for each channel and include the  FOR CHANNEL  channel  clause: This section describes how to disable GTID transactions on servers that are already online. This procedure does not require taking the server offline and is suited to use in production. However, if you have the possibility to take the servers offline when disabling GTIDs mode that process is easier. The process is similar to enabling GTID transactions while the server is online, but reversing the steps. The only thing that differs is the point at which you wait for logged transactions to replicate. Before you start, ensure that the servers meet the following pre-conditions: SET @@GLOBAL.GTID_MODE = ON_PERMISSIVE; STOP SLAVE [FOR CHANNEL ’channel’]; CHANGE MASTER TO MASTER_AUTO_POSITION = 1 [FOR CHANNEL ’channel’]; START SLAVE [FOR CHANNEL ’channel’]; Or from MySQL 8.0.22 / 8.0.23: STOP REPLICA [FOR CHANNEL ’channel’]; CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1 [FOR CHANNEL ’channel’]; START REPLICA [FOR CHANNEL ’channel’]; 17.1.4.3 Disabling GTID Transactions Online • All  servers in your topology must use MySQL 5.7.6 or later. You cannot disable GTID transactions online on any single server unless  all  servers which are in the topology are using this version. •All servers have  gtid_mode  set to  ON . •The  --replicate-same-server-id  option is not set on any server. You cannot disable GTID transactions if this option is set together with the  --log-slave-updates  option (which is the default) and binary logging is enabled (which is also the default). Without GTIDs, this combination of options causes infinite loops in circular replication. 1. Execute the following on each replica, and if you are using multi-source replication, do it for each channel and include the  FOR CHANNEL  channel clause: STOP SLAVE [FOR CHANNEL ’channel’]; CHANGE MASTER TO MASTER_AUTO_POSITION = 0, MASTER_LOG_FILE = file, \ MASTER_LOG_POS = position [FOR CHANNEL ’channel’]; START SLAVE [FOR CHANNEL ’channel’]; Or from MySQL 8.0.22 / 8.0.23: STOP REPLICA [FOR CHANNEL ’channel’]; CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 0, SOURCE_LOG_FILE = file, \ SOURCE_LOG_POS = position [FOR CHANNEL ’channel’]; START REPLICA [FOR CHANNEL ’channel’]; 2. On each server, execute: 3. On each server, execute: 3479