Last_IO_Errno: 1236 Last_IO_Error: Got fatal error 1236 from master when reading data from binary lo-优快云博客

本文讨论了如何处理MySQL复制过程中从错误位置恢复的问题，包括错误信息解析、重新设置位置点、跳过重复插入操作及重启复制流程等步骤。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 10.122.41.208
Master_User: replication
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000173
Read_Master_Log_Pos: 90376278
Relay_Log_File: mysql-relay-bin.001980
Relay_Log_Pos: 90376424
Relay_Master_Log_File: mysql-bin.000173
Slave_IO_Running: No
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table:
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error:
Skip_Counter: 0
Exec_Master_Log_Pos: 90376278
Relay_Log_Space: 90376726
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: 1236
Last_IO_Error: 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.000173' at 90376278, the last event read from '/mysql/binlog/mysql-bin.000173' at 4, the last byte read from '/mysql/binlog/mysql-bin.000173' at 4.'
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 11
1 row in set (0.00 sec)

mysql>

属于http://blog.youkuaiyun.com/mchdba/article/details/11208879的后续处理工作

比较一个笨的处理办法：

重新change position点，然后碰到重复insert的报错，就直接看position点，如果在90376278之前的，就skip掉，执行：

stop slave;

set global sql_slave_skip_counter=1;

start slave;

show slave status\G;