Case of Ha:gtid_mode configuration inconsistency in MySQL

1.1.1. Ha:gtid_mode Configuration Inconsistency

"Environment description"

msyql5.6.14

"Error Message"

The initial state master and slave both opened the enforce-gtid-consistency and Gtid-mode, and then changed both of them to off on master, at which point the slave error occurred:

last_io_error:the slave IO thread stopsbecause the master has @ @GLOBAL. Gtid_mode off and this server has@ @GLOBAL. Gtid_mode on

"Cause of the error"

MySQL's master and slave must both turn on or off the enforce-gtid-consistency and Gtid-mode functions, that is, to be consistent.

"Workaround"

Turn off the enforce-gtid-consistency and Gtid-mode features on the slave.

This column more highlights: http://www.bianceng.cn/database/MySQL/

Resources

Gtid-mode is used to set whether to turn on the Gtid function, if you want to turn on the Gtid function, you need to open both the Log-bin and Log_slave_updates functions, and also need to turn on the Enforce_gtid_consistency function. The Gtid_mode parameter can be set to ON, off, upgrade_step_1, upgrade_step_2 four values, where upgrade_step_1 and upgrade_step_2 are reserved for future MySQL possible new features, Doesn't make any sense to the current MYQL. At the same time, MySQL recommends turning off the Gtid_mode feature and the Enforce_gtid_consistency feature when Mysql_upgrade, because MySQL may operate a non-transactional MyISAM storage engine table during upgrade. can cause an error.