设为首页 - 加入收藏 应用网_丽江站长网 (http://www.0888zz.com)- 经验,大数据,运营,云主机,资讯,5G,云计算,站长网!
热搜: 创业 百度 阿里巴巴 移动互联网
当前位置: 主页 > 站长学院 > MySql教程 > 正文

MySQL ERROR Slave I O Found a Gtid_log_event or Previous

发布时间:2022-04-02 11:13 所属栏目:[MySql教程] 来源:互联网
导读:MySQL 5.6的复制中断,发生下面错误 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 writ
       MySQL 5.6的复制中断,发生下面错误
 
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))

【免责声明】本站内容转载自互联网,其相关言论仅代表作者个人观点绝非权威,不代表本站立场。如您发现内容存在版权问题,请提交相关链接至邮箱:bqsm@foxmail.com,我们将及时予以处理。

网友评论
推荐文章