600字范文,内容丰富有趣,生活中的好帮手!
600字范文 > MySQL5.1主从同步出现Relay log read failure错误解决方法【MySQL】

MySQL5.1主从同步出现Relay log read failure错误解决方法【MySQL】

时间:2023-09-21 16:15:52

相关推荐

MySQL5.1主从同步出现Relay log read failure错误解决方法【MySQL】

数据库|mysql教程

MySQL,MySQL5.1,主从同步,Relay,

数据库-mysql教程

众所周知MySQL5.1的Replication是比较烂的。MySQL的每一个版本更新关于同步方面每次都是可以看到一大堆。但MySQL 5.1性能是比较突出的。所以经不住诱惑使用MySQL 5.1。所以也要经常遇到一些Bug。如:

有价t5源码,vscode管理已有插件,ubuntu换语言,tomcat应用版本发布,c#链接sqlite字符串,网页爬虫与大数据分析是啥课,php统计访客,名优seo优化哪家好,刷网站pv软件,phpcms 模板变量lzw

mysql> show slave status\G

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.10.118

Master_User: repl_wu

Master_Port: 3306

Connect_Retry: 30

Master_Log_File: mysql-bin.005121

Read_Master_Log_Pos: 64337286

Relay_Log_File: relay-bin.003995

Relay_Log_Pos: 18446697137031827760

Relay_Master_Log_File: mysql-bin.005121

Slave_IO_Running: Yes

Slave_SQL_Running: No

Replicate_Do_DB:

Replicate_Ignore_DB:

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno: 1594

Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.

Skip_Counter: 0

Exec_Master_Log_Pos: 4

Relay_Log_Space: 64337901

Until_Condition: None

Until_Log_File:

Until_Log_Pos: 0

Master_SSL_Allowed: No

Master_SSL_CA_File:

Master_SSL_CA_Path:

Master_SSL_Cert:

Master_SSL_Cipher:

Master_SSL_Key:

Seconds_Behind_Master: NULL

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 0

Last_IO_Error:

Last_SQL_Errno: 1594

Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master’s binary log is corrupted (you can check this by running ‘mysqlbinlog’ on the binary log), the slave’s relay log is corrupted (you can check this by running ‘mysqlbinlog’ on the relay log), a network problem, or a bug in the master’s or slave’s MySQL code. If you want to check the master’s binary log or slave’s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS’ on this slave.

1 row in set (0.00 sec)

仿163ym源码,ubuntu如何删除主题,tomcat时区不对怎么办,爬虫安装与使用,php数组删除用什么函数,边际成本seolzw

Asp源码烧香网,vscode报错指向,国内ubuntu用的多吗,tomcat cmd中文,按照时间查询sqlite,淘宝地址选择插件,前端框架用运行吗,哥斯拉大战雷电爬虫,301跳转php,seo怎么理解,易语言如何写网站,织梦网页播放视频教程,手机牌价模板,stm8s 程序下载lzw

从上面可以看到是中继日值或是Master上的日值出问题了。

首先如果是中继日值坏掉,那只需要找到同步的时间点,然后重新同步,这样就可以有新的中继日值了。如果Master上的日值坏了就麻烦了。

从经验来看,这是中继日值出问题了。处理方法:

需要找到同步的点。

日值为:Master_Log_File: mysql-bin.005121,Relay_Master_Log_File: mysql-bin.005121以Relay_Master_Log_File为准,Master_Log_File为参考。

日值执行时间点:

Exec_Master_Log_Pos: 4

那么现在就可以:

mysql>stop slave;

mysql>change master to Master_Log_File=’mysql-bin.005121′, Master_Log_Pos=4;

mysql>start slave;

mysql>show slave status\G;

进行确认。

建议:

在使用MySQL-5.1.36以下的版本的同学,请尽快升级到MySQL-5.1.40 & MySQL-5.1.37sp1

本内容不代表本网观点和政治立场,如有侵犯你的权益请联系我们处理。
网友评论
网友评论仅供其表达个人看法,并不表明网站立场。