[MySQL Case] HA: GTID_MODE configuration inconsistent

1.1.1. HA: inconsistent GTID_MODE configurations

[Environment description]

Msyql5.6.14

[Error message]

In the initial state, both the Master and Slave enforce-gtid-consistency and gtid-mode are enabled, and both of them are changed to off. In this case, Slave reports an error:

Last_IO_Error: The slave IO thread stopsbecause the master has @ GLOBAL. GTID_MODE OFF and this server has @ GLOBAL. GTID_MODE ON

[Error cause]

MySQL Master and Slave must both enforce-gtid-consistency and gtid-mode must be enabled or disabled, that is, they must be consistent.

[Solution]

Disable the enforce-gtid-consistency and gtid-mode functions on Slave.

 

[References]

Gtid-mode is used to set whether to enable the GTID function. If you want to enable the GTID function, you need to enable both log-bin and log_slave_updates functions, and enforce_gtid_consistency functions. The gtid_mode parameter can be set to on, off, upgrade_step_1, and upgrade_step_2. upgrade_step_1 and upgrade_step_2 are reserved for potential new functions of mysql in the future and have no significance for the current myql. At the same time, it is recommended that gtid_mode and enforce_gtid_consistency be disabled during mysql_upgrade, because mysql may operate non-transactional MyISAM storage engine tables during upgrade, which may cause an error.