3分钟解决MySQL 1032 主从错误(转)

转自  https://blog.51cto.com/suifu/1845457

3分钟解决MySQL 1032主从错误

Part1:写在最前

1032错误----现在生产库中好多数据,在从库误删了,生产库更新后找不到了,现在主从不同步了,再跳过错误也没用,因为没这条,再更新还会报错

解决方案

Part1:临时方案

mysql> stop slave;
Query OK, 0 rows
affected (0.00 sec)

mysql> set global sql_slave_skip_counter=1;
Query OK, 0 rows
affected (0.00 sec)

mysql> start slave;
Query OK, 0 rows
affected (0.00 sec)

Part2:永久方案

end_log_pos 有了它,根据pos值,直接就能找到,找到delete那条数据,反做(变成insert)

故障模拟

HE1从库误删

mysql> delete from helei where id=3;
Query OK, 1 row
affected (0.29 sec)

mysql> select * from helei;
+----+------+
| id | text |
+----+------+
|  1 | aa
|
|  2 | bb
|
|  4 | ee
|
|  5 | ff
|
|  6 | gg
|
|  7 | hh
|
+----+------+
6 rows in set (0.00
sec)

mysql> show slave status\G;
***************************
1. row ***************************
               Slave_IO_State: Waiting for
master to send event
                  Master_Host: 192.168.1.250
                  Master_User: mysync
                  Master_Port: 2503306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000005
          Read_Master_Log_Pos: 3711
               Relay_Log_File:
HE1-relay-bin.000007
                Relay_Log_Pos: 484
        Relay_Master_Log_File: mysql-bin.000005
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

此时从库状态是正常的,但一旦主库对该条记录进行操作

HE3主库更新从库刚刚误删的数据

mysql> update helei set text=‘ccc‘ where id=3;
Query OK, 1 row
affected (0.01 sec)
Rows matched: 1  Changed: 1
Warnings: 0

mysql> select * from helei;
+----+------+
| id | text |
+----+------+
|  1 | aa
|
|  2 | bb
|
|  3 | ccc
|
|  4 | ee
|
|  5 | ff
|
|  6 | gg
|
|  7 | hh
|
+----+------+
7 rows in set (0.00
sec)

HE1从库报错

mysql> show slave status\G;
***************************
1. row ***************************
               Slave_IO_State: Waiting for
master to send event
                  Master_Host: 192.168.1.250
                  Master_User: mysync
                  Master_Port: 2503306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000005
          Read_Master_Log_Pos: 3918
               Relay_Log_File:
HE1-relay-bin.000007
                Relay_Log_Pos: 484
        Relay_Master_Log_File: mysql-bin.000005
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 1032
                   Last_Error: Could not
execute Update_rows event on table test.helei; Can‘t find record in ‘helei‘,
Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event‘s master log
mysql-bin.000005, end_log_pos 3887
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 3711
              Relay_Log_Space: 1626
              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: 0
                Last_IO_Error:
               Last_SQL_Errno: 1032

Last_SQL_Error: Could not execute Update_rows event on table test.helei;
Can‘t find record in ‘helei‘, Error_code: 1032; handler error
HA_ERR_KEY_NOT_FOUND; the event‘s master log mysql-bin.000005, end_log_pos 3887(这个mysql-bin.000005,end_log_pos
3887是主库的)
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 2503306
                  Master_UUID:
f7c96432-f665-11e5-943f-000c2967a454
             Master_Info_File:
/data/mysql/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State:
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp: 160331 09:25:02
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0
1 row in set (0.00
sec)

此时主从又不同步了,如果还去执行跳过错误操作,主从恢复同步,而且状态均为yes,但!这并不能解决该问题,如果主库又更新该条记录,那么还是会报相同错误,而且pos号还会变,这就导致了恢复时你不知道前一条的pos号,导致丢失数据。

mysql> stop slave;
Query OK, 0 rows
affected (0.00 sec)

mysql> set global sql_slave_skip_counter=1;
Query OK, 0 rows
affected (0.00 sec)

mysql> start slave;
Query OK, 0 rows
affected (0.00 sec)

mysql> select * from helei;
+----+--------+
| id | text   |
+----+--------+
|  1 | aa
|
|  2 | bb
|
|  4 | ee
|
|  5 | ff
|
|  6 | gg
|
|  7 | hh
|
|  8 | helei1 |
+----+--------+
7 rows in set (0.00 sec)

mysql> show slave status\G;
***************************
1. row ***************************
               Slave_IO_State: Waiting for
master to send event
                  Master_Host: 192.168.1.250
                  Master_User: mysync
                  Master_Port: 2503306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000005
          Read_Master_Log_Pos: 4119
               Relay_Log_File:
HE1-relay-bin.000008
                Relay_Log_Pos: 283
        Relay_Master_Log_File: mysql-bin.000005
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

这里虽然通过跳过错误达到恢复主从同步,但如果主库又对该条记录更新

mysql> update helei set text=‘cccc‘ where id=3;
Query OK, 1 row
affected (0.00 sec)
mysql> show slave status\G;
***************************
1. row ***************************
               Slave_IO_State: Waiting for
master to send event
                  Master_Host: 192.168.1.250
                  Master_User: mysync
                  Master_Port: 2503306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000005
          Read_Master_Log_Pos: 4328
               Relay_Log_File:
HE1-relay-bin.000008
                Relay_Log_Pos: 283
        Relay_Master_Log_File: mysql-bin.000005
             Slave_IO_Running: Yes

Slave_SQL_Running: No
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:

Last_Errno: 1032

Last_Error: Could not execute Update_rows event on table test.helei;
Can‘t find record in ‘helei‘, Error_code: 1032; handler error
HA_ERR_KEY_NOT_FOUND; the event‘s master log mysql-bin.000005, end_log_pos 4297
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 4119
              Relay_Log_Space: 1435
              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: 0
                Last_IO_Error:

Last_SQL_Errno: 1032

Last_SQL_Error: Could not execute Update_rows event on table test.helei;
Can‘t find record in ‘helei‘, Error_code: 1032; handler error
HA_ERR_KEY_NOT_FOUND; the event‘s master log mysql-bin.000005, end_log_pos 4297
  Replicate_Ignore_Server_Ids:
             Master_Server_Id: 2503306
                  Master_UUID:
f7c96432-f665-11e5-943f-000c2967a454
             Master_Info_File:
/data/mysql/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State:
           Master_Retry_Count: 86400
                  Master_Bind:
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp: 160331 09:33:34
               Master_SSL_Crl:
           Master_SSL_Crlpath:
           Retrieved_Gtid_Set:
            Executed_Gtid_Set:
                Auto_Position: 0

原文地址:https://www.cnblogs.com/xiaohanlin/p/10728165.html

时间: 2024-10-14 08:34:23

3分钟解决MySQL 1032 主从错误(转)的相关文章

如何快速解决MySQL 1032 主从错误

3分钟解决MySQL 1032主从错误 Part1:写在最前1032错误----现在生产库中好多数据,在从库误删了,生产库更新后找不到了,现在主从不同步了,再跳过错误也没用,因为没这条,再更新还会报错 解决方案 Part1:临时方案 mysql> stop slave;Query OK, 0 rowsaffected (0.00 sec) mysql> set global sql_slave_skip_counter=1;Query OK, 0 rowsaffected (0.00 sec)

解决mysql 1864 主从错误

从字面意思看了一下是因为slave_pending_jobs_size_max默认值为16777216(16MB),但是slave接收到的slave_pending_jobs_size_max为17085453(17M): 解决方案 从库执行如下SQL mysql>stop slave; mysql>set global slave_pending_jobs_size_max=20000000; mysql> start slave; #在多线程复制时,在队列中Pending的事件所占用

【mysql】service mysql start出错,mysql启动不了,解决mysql: unrecognized service错误

service MySQL start出错,mysql启动不了,解决mysql: unrecognized service错误的方法如下: [[email protected] ~]# service mysql startmysql: unrecognized service[[email protected] ~]# service mysql restartmysql: unrecognized service [[email protected] ~]# rpm -q mysql   查

service mysql start出错,mysql启动不了,解决mysql: unrecognized service错误

service mysql start出错,mysql启动不了,解决mysql: unrecognized service错误的方法如下: [[email protected] ~]# service mysql startmysql: unrecognized service[[email protected] ~]# service mysql restartmysql: unrecognized service [[email protected] ~]# rpm -q mysql 查询发

重置密码解决MySQL for Linux错误 ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

一般这个错误是由密码错误引起,解决的办法自然就是重置密码. 假设我们使用的是root账户. 1.重置密码的第一步就是跳过MySQL的密码认证过程,方法如下: #vim /etc/my.cnf(注:windows下修改的是my.ini) 在文档内搜索mysqld定位到[mysqld]文本段:/mysqld(在vim编辑状态下直接输入该命令可搜索文本内容) 在[mysqld]后面任意一行添加"skip-grant-tables"用来跳过密码验证的过程,如下图所示: 保存文档并退出: #:w

解决mysql 数据库主从不同步

今天发现Mysql的主从数据库没有同步 先上Master库: mysql>show processlist;   查看下进程是否Sleep太多.发现很正常. show master status; 也正常. mysql> show master status; +-------------------+----------+--------------+-------------------------------+ | File              | Position | Binlo

重置密码解决MySQL for Linux错误 ERROR 1045 (28000):

一般这个错误是由密码错误引起,解决的办法自然就是重置密码.假设我们使用的是root账户.1,停止mysql服务service mysqld stop2,找到my.cnf文件 3,修改配置文件无密码登录vi /etc/my.cnf在最尾部加上skip-grant-tables保存(:wq)4,启动mysqlsystemctl start mysqld.service mysqld start5,登录musqlmysql -u root此处注意不要加-p6,修改密码,mysql5.7用此语法use

解决MySQL主从不同步问题

解决mysql主从不同步 今天发现Mysql的主从数据库没有同步 先上Master库: mysql>show processlist;   查看下进程是否Sleep太多.发现很正常. show master status; 也正常. mysql> show master status; +-------------------+----------+--------------+-------------------------------+ | File              | Pos

MySQL跳过主从错误工具(mysqlha_skiperror.sh)

工具名称:mysqlha_skiperror.sh 工具用途:用于MySQL跳过主从错误 工具参数:options: -P port   指定端口                   -N number   指定跳过错误次数  不指定默认为10次(如果不知道可以设置大一些,会记录log) -C      error code  Take ,  as the separator  指定跳过错误的状态码 可以跳过多个以,分隔 工具示例: mysqlha_skiperror.sh -P 4444 -C