mysql 8.0.25 x86 64 centos7.8 2022-10-12T17:01:18.188591+08:00 5 [System] [MY-010562] [Repl] Slave I/O thread for channel '': connected to master 'repl@idc-mysql-113-40:3306',replication started in log 'idc-mysql-113-40.000849' at position 196 2022-10-12T17:01:18.190901+08:00 12 [Note] [MY-010051] [Server] Event Scheduler: scheduler thread started with id 12 2022-10-12T17:01:18.192144+08:00 0 [Note] [MY-011240] [Server] Plugin mysqlx reported: 'Using SSL configuration from MySQL Server' 2022-10-12T17:01:18.192666+08:00 0 [Note] [MY-011243] [Server] Plugin mysqlx reported: 'Using OpenSSL for TLS connections' 2022-10-12T17:01:18.192843+08:00 0 [System] [MY-010931] [Server] /usr/local/mysql/bin/mysqld: ready for connections. Version: '8.0.25' socket: '/data/mysql3306/tmp/mysql3306.sock' port: 3306 MySQL Community Server - GPL. 2022-10-12T17:01:18.199065+08:00 6 [Note] [MY-010581] [Repl] Slave SQL thread for channel '' initialized, starting replication in log 'idc-mysql-113-40.000849' at position 196, relay log '/data/mysql3306/relaylog/idc-mysql-113-41.000003' position: 4 2022-10-12T17:01:20.358076+08:00 5 [ERROR] [MY-011178] [Repl] Missing magic number for semi-sync packet, packet len: 46. 2022-10-12T17:01:20.358110+08:00 5 [ERROR] [MY-010207] [Repl] Run function 'after_read_event' in plugin 'rpl_semi_sync_slave' failed 2022-10-12T17:01:20.358124+08:00 5 [ERROR] [MY-013117] [Repl] Slave I/O for channel '': Fatal error: Failed to run 'after_read_event' hook, Error_code: MY-013117 2022-10-12T17:01:20.358132+08:00 5 [Note] [MY-010570] [Repl] Slave I/O thread exiting for channel '', read up to log 'idc-mysql-113-40.000849', position 196 2022-10-12T17:01:31.239736+08:00 0 [Note] [MY-011946] [InnoDB] Buffer pool(s) load completed at 221012 17:01:31 2022-10-12T17:01:33.183337+08:00 6 [Note] [MY-010596] [Repl] Error reading relay log event for channel '': slave SQL thread was killed 2022-10-12T17:01:33.183645+08:00 6 [Note] [MY-010587] [Repl] Slave SQL thread for channel '' exiting, replication stopped 这个问题在那个版本修复了? replication_sender_observe_commit_only 我把这个参数关了,重新操作了故障之前的操作,现在没有出现io线程不能启动 |
合作电话:010-64087828
社区邮箱:greatsql@greatdb.com