MySQL 5.7What about the copy error Client requested master to start replication from impossible

This article will explain in detail how to copy the error report Client requested master to start replication from impossible in MySQL 5.7. the editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Information in the error log

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 from master when reading data from binary log 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_log/mysql-bin.000003' at 4, Error_code: 1236

Reason for reporting an error

When executing the change master statement, the master_log_file in it is written incorrectly

Solution method

In the change master statement, write the correct master_log_file

This is the end of this article on "MySQL 5.7 copy error Client requested master to start replication from impossible". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it out for more people to see.