MySQL 5.7复制报错Client requested master to start replication from impossible怎么办

这篇文章将为大家详细讲解有关MySQL 5.7复制报错Client request免费主机域名ed master to start replication from impossible怎么办，小编觉得挺实用的，因此分享给大家做个参考，希望大家阅读完这篇文章后可以有所收获。
错误日志中的信息
2017-12-12T07:41:47.070228Z 57896 [ERROR] Error reading packet from server for channel ‘master_4’: Client requested master to start replication from impossible position; the first event ‘mysql-bin.000003’ at 31342251, the last event read from ‘/data/db_log/mysql-bin.000003’ at 4, the last byte read from ‘/data/db_log/mysql-bin.000003’ at 4. (server_errno=1236)

2017-12-12T07:41:47.077618Z 57896 [ERROR] Slave I/O for channel ‘master_4’: Got fatal error 1236 from master when reading data from binary log: ‘Client requested master to start replication from impossible position; the first event ‘mysql-bin.000003’ at 31342251, the last event read from ‘/data/db_log/mysql-bin.000003’ at 4, the last byte read from ‘/data/db_l免费主机域名og/mysql-bin.000003′ at 4.’, Error_code: 1236

报错原因
执行 change master 语句时，里面的master_log_file 写的不正确

解决方法
在 change master 语句里，写上正确的master_log_file
关于“MySQL 5.7复制报错Client requested master to start replication from impossible怎么办”这篇文章就分享到这里了，希望以上内容可以对大家有一定的帮助，使各位可以学到更多知识，如果觉得文章不错，请把它分享出去让更多的人看到。

相关推荐: Innodb下null ” ‘ ‘的存储表现有什么不同

小编给大家分享一下Innodb下null ” ‘ ‘的存储表现有什么不同，希望大家阅读完这篇文章之后都有所收获，下面让我们一起去探讨吧！null ：nullbits 位图上的区别。‘’：可变字节多一个字节。‘ ‘：可变字节多一个字节且实际数据区域为0X20多…