Database Replication Errors in Classic HA Controller

Update the replica's starting position with the primary server's GTID to ensure both servers are synchronized.

1. Log in to the Controller HA's primary server and run the following command:
   CODECopy

   SHOW VARIABLES like 'gtid_executed';

   SHOW VARIABLES like 'gtid_executed';

   Sample Output:

   CODECopy

   mysql> SHOW VARIABLES like 'gtid_executed'; +---------------+---------------------------------------------+ | Variable_name | Value | +---------------+---------------------------------------------+ | gtid_executed | fe90e0c1-47ba-11f1-a1d0-022caf0947f7:1-6302 | +---------------+---------------------------------------------+ 1 row in set (0.01 sec)

   mysql>  SHOW VARIABLES like 'gtid_executed';
   +---------------+---------------------------------------------+
   | Variable_name | Value                                       |
   +---------------+---------------------------------------------+
   | gtid_executed | fe90e0c1-47ba-11f1-a1d0-022caf0947f7:1-6302 |
   +---------------+---------------------------------------------+
   1 row in set (0.01 sec)

   Note: You require this gtid_executed value to use it in the next step.
2. Log in to secondary Controller MySQL and run the following command:
   PYTHONCopy

   STOP REPLICA; -- Use the gtid_executed value from the previous step. SET GLOBAL gtid_purged = '<gtid_executed_value>'; CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1; START REPLICA;

   STOP REPLICA;
   -- Use the gtid_executed value from the previous step.
   SET GLOBAL gtid_purged = '<gtid_executed_value>'; 
   
   CHANGE REPLICATION SOURCE TO SOURCE_AUTO_POSITION = 1;
   
   START REPLICA;