服务器 Gind.cn
  1. 服务器 Gind.cn
  3. MySQL复制：从属I / O线程不断死亡并开始备份
Intereting Posts
Win Server 2008挂在“应用计算机设置” iptables端口转发（prerouting端口80）和防火墙不能一起工作 从现有configuration创buildkickstartconfiguration文件 设置基于证书的VPN接入点 BIND DNS：如何覆盖由$ GENERATE指令生成的RR？ 只能在EC2实例中连接到端口80 如何判断grub是否安装在设备上？ Virtualbox虚拟机（由Vagrant产生）运行，但无法访问。 现在怎么办？ 使用RegEx的Exchange 2013邮件stream规则 目录树的本地全文索引，是grep -R的更快select 如何在没有DC的情况下删除Exchange 2007angular色？ 将会话文件存储在PHP中的不同目录中 将最新的ADMX（＆lang文件）复制到AD Central Store有何危险？ 是否有可能为几个本地主机configurationApache？ Google Apps密码更改未反映在所有设备上

MySQL复制：从属I / O线程不断死亡并开始备份

我有MySQL在两个MySQL数据库之间运行Debian 5（Lenny）。 数据正在两台机器之间传输，但其中一个正在logging从机I / O线程正在不断死亡，然后马上重新初始化的事实。

有问题的日志条目的示例： 

Jul 19 08:15:43 foo-db2 mysqld[22419]: 110719 8:15:43 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000002' at position 2107802, relay log '/var/log/mysql/mysql-relay-bin.018257' position: 235 Jul 19 08:15:43 foo-db2 mysqld[22419]: 110719 8:15:43 [Note] Slave I/O thread: connected to master '[email protected]:3306', replication started in log 'mysql-bin.000002' at position 2107802 Jul 19 08:15:44 foo-db2 mysqld[22419]: 110719 8:15:44 [Note] Slave I/O thread killed while reading event Jul 19 08:15:44 foo-db2 mysqld[22419]: 110719 8:15:44 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000002', position 2107802 Jul 19 08:15:44 foo-db2 mysqld[22419]: 110719 8:15:44 [Note] Error reading relay log event: slave SQL thread was killed Jul 19 08:15:46 foo-db2 mysqld[22419]: 110719 8:15:46 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000002' at position 2107802, relay log '/var/log/mysql/mysql-relay-bin.018258' position: 235 Jul 19 08:15:46 foo-db2 mysqld[22419]: 110719 8:15:46 [Note] Slave I/O thread: connected to master '[email protected]:3306', replication started in log 'mysql-bin.000002' at position 2107802 Jul 19 08:15:47 foo-db2 mysqld[22419]: 110719 8:15:47 [Note] Slave I/O thread killed while reading event Jul 19 08:15:47 foo-db2 mysqld[22419]: 110719 8:15:47 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000002', position 2107802 Jul 19 08:15:47 foo-db2 mysqld[22419]: 110719 8:15:47 [Note] Error reading relay log event: slave SQL thread was killed

但是，即使有上述错误，机器“foo-db2”也跟上了“foo-db1”： 

 mysql@foo-db2> SHOW SLAVE STATUS\G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 10.10.95.28 Master_User: replicator Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000002 Read_Master_Log_Pos: 2229610 Relay_Log_File: mysql-relay-bin.018379 Relay_Log_Pos: 235 Relay_Master_Log_File: mysql-bin.000002 Slave_IO_Running: Yes Slave_SQL_Running: Yes [...] mysql@foo-db1> SHOW MASTER STATUS; +------------------+----------+--------------+------------------+ | File | Position | Binlog_Do_DB | Binlog_Ignore_DB | +------------------+----------+--------------+------------------+ | mysql-bin.000002 | 2229610 | | | +------------------+----------+--------------+------------------+ 1 row in set (0.00 sec)

也就是说，“SHOW SLAVE STATUS”在“Slave_IO_Running = Yes”和“Slave_SQL_Running = Yes”之间输出yo-yos，并且是“否”

最后，“mysql-relay-bin。######”文件每隔几秒不断更高，但文件总是235字节： 

 root@foo-db2:/var/log/mysql# mysqlbinlog mysql-relay-bin.0* /*!40019 SET @@session.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; DELIMITER /*!*/; # at 4 #110719 8:25:40 server id 2 end_log_pos 98 Start: binlog v 4, server v 5.0.51a-24+lenny4-log created 110719 8:25:40 # at 98 #691231 19:00:00 server id 1 end_log_pos 0 Rotate to mysql-bin.000002 pos: 2229610 # at 141 #110719 6:25:02 server id 1 end_log_pos 0 Start: binlog v 4, server v 5.0.51a-24+lenny4-log created 110719 6:25:02 DELIMITER ; # End of log file ROLLBACK /* added by mysqlbinlog */; /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;