MySQL [ERROR] Slave I/O: Found a Gtid_log_event or Previous_gtids_log_event
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))
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26506993/viewspace-2216960/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 故障案例:主從同步報錯Fatal error: The slave I/O thread stops because master and slave have equal MySQL server主從同步ErrorthreadASTMySqlServer
- The slave I/O thread stops because master and slave have equal MySQL server UUIDthreadASTMySqlServerUI
- mysql-python安裝時Environment Error: mysql_config not foundMySqlPythonError
- MySQL之磁碟I/O過高排查MySql
- org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.SQLExceptionErrorWhile
- 執行SQL發生錯誤!錯誤:disk I/O errorSQLError
- 計算機I/O與I/O模型計算機模型
- MySQL 配置InnoDB主執行緒I/O速率MySql執行緒
- I/O流
- Java I/OJava
- MySQL 5.6複製報錯Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND;MySqlError
- yarn add @fortawesome/Font Awesome-free 之後 報錯 EIO: i/o errorYarnError
- MySQL 配置後臺InnoDB I/O執行緒數MySql執行緒
- Python教程:精簡概述I/O模型與I/O操作Python模型
- 關於I/O
- c++ I/OC++
- 【java】I/O流Java
- Java(8)I/OJava
- MySQL在刪除表時I/O錯誤原因分析MySql
- Look what I found out.
- MySQL 5.7從庫報錯exceeds of slave_pending_jobs_size_max. Error_code: 1864MySqlError
- ERROR: No abbreviations files found in ...nonbreaking_prefixesError
- [PM2][ERROR] Process XXX not foundError
- JAVA I/O系統Java
- 系統級 I/O
- Google I/O Extend 2018Go
- 網路I/O模型模型
- NodeJs 非同步 I/ONodeJS非同步
- 理解I/O Completion Port
- python 非同步 I/OPython非同步
- 02. I/O 操作
- Java 非同步 I/OJava非同步
- Hadoop的I/O操作Hadoop
- Error on opening a connection to slave1:33061 on local port: 33061Error
- mysql 8 報錯 ERROR 1872 (HY000): Slave failed to initialize relay log info structure from the repositoryMySqlErrorAIStruct
- Linux下的5種I/O模型與3組I/O複用Linux模型
- ORACLE OMS啟動失敗之BEA-300040 I/O error while writing node manager statusOracleErrorWhile
- PBOOTCMS網站程式提示“執行SQL發生錯誤!錯誤:DISK I/O ERROR”boot網站SQLError