read_master_log_pos是从库已经读取并且准备执行的二进制日志的位置,而exec_master_log_pos是从库已经执行完的二进制日志的位置。当从库处理完一个事件后,会将exec_master_log_pos更新为该事件的位置。但是由于网络等原因,从库可能会出现延迟,导致exec_master_log_pos落后于read_master_log_pos。 解决方案 要解...
1) The position, ON THE MASTER, from which the I/O thread is reading:Master_Log_File/Read_Master_Log_Pos. ---相对于主库,从库读取主库的二进制日志的位置,是IO线程 2) The position, IN THE RELAY LOGS, at which the SQL thread is executing:Relay_Log_File/Relay_Log_Pos ---相对于从库...
但是从机上的 read_master_log_pos 落后于 主机上的position的, 我stop slave,再start就正常了; 想问下老师:1.read_master_log_pos 是不是一定会和position一致; 2.如何做这种情况的监控,比如我可以在从机写个crontab脚本监控running状态,但是我没有办法在从机上取到master的postition 3. 目前在mysql的日志里...
The position, ON THE MASTER, from which the I/O thread is reading: Master_Log_File/Read_Master_Log_Pos. —–相对于主库,从库读取主库的二进制日志的位置,是IO线程 The position, IN THE RELAY LOGS, at which the SQL thread is executing: Relay_Log_File/Relay_Log_Pos —-相对于从库,是从...
log by slave I/O thread even if its rows events are discarded. But it is not displayed by MYSQLBINLOG and SHOW RELAYLOG EVENTS. However, the Read_Master_Log_Pos displayed by SHOW SLAVE STATUS is at the end of the Table_map_Log_event. After the patch, the Table_map_log_event will...