MySQL 5.6的复制中断，发生下面错误
10年积累的网站设计制作、成都网站设计经验，可以快速应对客户对网站的新想法和需求。提供各种问题对应的解决方案。让选择我们的客户得到更好、更有力的网络服务。我虽然不认识你，你也不认识我。但先网站设计后付款的网站建设流程，更有铁西免费网站建设让你可以放心的选择与我们合作。
2018-10-18 12:20:02 15374 [ERROR] Slave I/O: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF. Error_code: 1784 2018-10-18 12:20:02 15374 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Error_code: 1595 2018-10-18 12:20:02 15374 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000012', position 123 2018-10-18 13:57:41 15374 [Note] Error reading relay log event: slave SQL thread was killed 2018-10-18 13:57:44 15374 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information. 2018-10-18 13:57:44 15374 [Warning] Slave SQL: If a crash happens this configuration does not guarantee that the relay log info will be consistent, Error_code: 0 2018-10-18 13:57:44 15374 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000012' at position 123, relay log './mysqld3319-relay-bin.000004' position: 286 2018-10-18 13:57:44 15374 [Note] Slave I/O thread: connected to master 'backuper@10.156.15.1:3306',replication started in log 'mysql-bin.000012' at position 123 2018-10-18 13:57:45 15374 [ERROR] Slave I/O: Found a Gtid_log_event or Previous_gtids_log_event when @@GLOBAL.GTID_MODE = OFF. Error_code: 1784 2018-10-18 13:57:45 15374 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Error_code: 1595
报错原因：
从MySQL 5.7向较低版本的MySQL 5.6搭建复制时，会触发这个错误。
# mysqld -V mysqld Ver 5.6.20 for Linux on x86_64 (MySQL Community Server (GPL))
解决方法：
使用高版本的MySQL 5.6或5.7创建复制主机。
[root@db-backup-all ~]# /opt/mysql_56_40/bin/mysqld -V /opt/mysql_56_40/bin/mysqld Ver 5.6.40 for linux-glibc2.12 on x86_64 (MySQL Community Server (GPL))