mysql主从同步问题整理

2024年1月5日 84次阅读 来源: Victorchi

今早mysql同步失败,主数据库有530W而从数据库只有去350W,幸亏是做备份要不然这个就是个事故了.
问题如下:
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.

解决方法如下:

  • 我尝试重新配置了下链接,

mysql> CHANGE MASTER TO

-> MASTER_HOST='master_host_name',

-> MASTER_USER='replication_user_name',

-> MASTER_PASSWORD='replication_password',

-> MASTER_LOG_FILE='recorded_log_file_name',

然后出现了,新的错误.

       Slave_IO_Running: No
      Slave_SQL_Running: Yes
          Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from position > file size'**

  • 后来我尝试了重新配置了position下位置

mysql> stop slave; 
mysql> change master to master_log_file='mysql-bin.000011',master_log_pos=203; 
mysql> start slave; 
#  查看状态
show slave status\G 
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 121.196.207.230
                  Master_User: root
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000037
          Read_Master_Log_Pos: 12367642
               Relay_Log_File: DESKTOP-9EVDGPS-relay-bin.000002
                Relay_Log_Pos: 127713
        Relay_Master_Log_File: mysql-bin.000037
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

成功了,但是问题是,目前不清楚这个方案会不导致数据同步出错,我需要以后检验一下.

    原文作者：Victorchi
    原文地址: https://segmentfault.com/a/1190000012106287
    本文转自网络文章，转载此文章仅为分享知识，如有侵权，请联系博主进行删除。
点赞