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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- [ERROR] Slave I/O: Replication event checksum Error_code: 1743Error
- 故障案例:主從同步報錯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
- sloaris 出現“mount: I/O error”錯誤Error
- error:slave communication error with ASMErrorASM
- ERROR: slave communication error with ASMErrorASM
- mysql_slave :Error_code: 1593解決MySqlError
- MySQL之磁碟I/O過高排查MySql
- 【Mysql】Slave_SQL_Running: No:Last_Error: Error :1032/1062MySqlASTError
- MysqL錯誤之_ERROR! MySQL server PID file could not be found!MySqlErrorServer
- Veritas Quick I/O and Cached Quick I/OUI
- 【MySQL】5.6.x InnoDB Error Table mysql.innodb_table_stats not foundMySqlError
- 計算機I/O與I/O模型計算機模型
- I/O埠和I/O記憶體記憶體
- 執行SQL發生錯誤!錯誤:disk I/O errorSQLError
- 【Mysql】ERROR 1872 (HY000): Slave failed to initialize relay log infoMySqlErrorAI
- MySQL 配置InnoDB主執行緒I/O速率MySql執行緒
- Java I/OJava
- MySQL master/slaveMySqlAST
- MySQL新建SlaveMySql
- mysql-python安裝時Environment Error: mysql_config not foundMySqlPythonError
- Error 15: File not found for RedhatErrorRedhat
- MySQL 配置後臺InnoDB I/O執行緒數MySql執行緒
- Java(8)I/OJava
- 【java】I/O流Java
- Java I/O流Java
- 檔案I/O
- I/O基礎
- java的I/OJava
- c++ I/OC++
- org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.SQLExceptionErrorWhile
- 【Mysql】Slave_IO_Running: No---Got fatal error 1236 from masterMySqlGoErrorAST
- MYSQL 配置slave故障MySql
- MySql的Master/SlaveMySqlAST
- MySQL 5.6複製報錯Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND;MySqlError
- Python教程:精簡概述I/O模型與I/O操作Python模型
- Direct I/O (DIO) and Concurrent I/O (CIO) on AIX 5LAI
- goldengate extract abended unable to queue I/O, I/O beyond file sizeGo