MySQL复制应用中继日志解析

本文涉及的产品
云数据库 RDS MySQL,集群系列 2核4GB
推荐场景:
搭建个人博客
RDS MySQL Serverless 基础系列,0.5-2RCU 50GB
RDS MySQL Serverless 高可用系列,价值2615元额度,1个月
简介:

SQL线程应用中继日志,在binlog_format是row格式的时候,是居于主键更新,下面结合一张图来证明

从一个大神那边得到一张图片,SQL线程应用中继日志流程,下面就实验验证一下:(PS,我个人认为这张图binlog_format为ROW格式是正确的)

 

 

 

2.验证有PK表情况

在主库创建表结构

CREATE TABLE `table_pk` (
`id`  int(11) NOT NULL ,
`name`  varchar(20) NOT NULL ,
`age`  tinyint NOT NULL ,
`sex`  tinyint NOT NULL COMMENT '0,man,1,woman' ,

PRIMARY KEY (`id`)
) ENGINE=InnoDB;

插入测试数据

insert into table_pk (`id`,`name`,`age`,`sex`) values(111,'zhangsan',20,0);
insert into table_pk (`id`,`name`,`age`,`sex`) values(222,'lisi',22,1);
insert into table_pk (`id`,`name`,`age`,`sex`) values(333,'wangwu',22,1);
insert into table_pk (`id`,`name`,`age`,`sex`) values(444,'lilei',32,0);
insert into table_pk (`id`,`name`,`age`,`sex`) values(555,'hanmeimei',30,1);

(dg6)root@localhost [(none)]> use mytest;

(dg6)root@localhost [mytest]> select * from table_pk;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg6)root@localhost [mytest]> show global variables like '%binlog_format%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| binlog_format | ROW   |
+---------------+-------+
row in set (0.00 sec)
那么我们去从库看看
(dg7)root@localhost [mytest]> select * from table_pk;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> show global variables like '%binlog_format%';
+--------------------------+-------------------+
| Variable_name            | Value             |
+--------------------------+-------------------+
| binlog_format            | ROW               |
+--------------------------+-------------------+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 4469
               Relay_Log_File: dg7-relay-bin.000002
                Relay_Log_Pos: 4681
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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: 4469
              Relay_Log_Space: 4883
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-17
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-9,
b888e1ea-9739-11e4-a24e-000c29b24887:1-17
                Auto_Position: 1
row in set (0.00 sec)

数据是复制过来的,MySQL主从复制是正常的,那么我们为了验证MySQL复制SQL线程是居于刚才那张图的流程,有主键,就按主键更新匹配更新记录。

那么我们在从库修改一行数据,故意制造不一致。

(dg7)root@localhost [mytest]> UPDATE `table_pk` SET `name`='laowang' WHERE `id`=333;
Query OK, 0 rows affected (0.00 sec)
Rows matched: 1  Changed: 0  Warnings: 0

(dg7)root@localhost [mytest]> select * from table_pk;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | laowang   |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)
这时候主从数据不一致了
主库
(dg6)root@localhost [mytest]> select * from table_pk where id=333;
+-----+--------+-----+-----+
| id  | name   | age | sex |
+-----+--------+-----+-----+
| 333 | wangwu |  22 |   1 |
+-----+--------+-----+-----+
row in set (0.00 sec)

从库
(dg7)root@localhost [mytest]> select * from table_pk where id=333;
+-----+---------+-----+-----+
| id  | name    | age | sex |
+-----+---------+-----+-----+
| 333 | laowang |  22 |   1 |
+-----+---------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]>
那么,我们在主库更新一行数据。
(dg6)root@localhost [mytest]> UPDATE `table_pk` SET `name`='wangzi' WHERE `id`=333;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg6)root@localhost [mytest]> select * from table_pk where id=333;
+-----+--------+-----+-----+
| id  | name   | age | sex |
+-----+--------+-----+-----+
| 333 | wangzi |  22 |   1 |
+-----+--------+-----+-----+
row in set (0.00 sec)
我们来看一下从库状态,是不是主库的更新给复制过来了,见证奇迹的时候到了
###############################################
(dg7)root@localhost [mytest]> select * from table_pk where id=333;
+-----+---------+-----+-----+
| id  | name    | age | sex |
+-----+---------+-----+-----+
| 333 | laowang |  22 |   1 |
+-----+---------+-----+-----+
row in set (0.00 sec)
#########################  神奇的是主库的更新过来了#############################################

(dg7)root@localhost [mytest]> select * from table_pk where id=333;
+-----+--------+-----+-----+
| id  | name   | age | sex |
+-----+--------+-----+-----+
| 333 | wangzi |  22 |   1 |
+-----+--------+-----+-----+
row in set (0.00 sec)

#########################那么看一下MySQL主从复制状态看看,也是正常的######################
(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 5249
               Relay_Log_File: dg7-relay-bin.000002
                Relay_Log_Pos: 5461
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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: 5249
              Relay_Log_Space: 5663
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-20
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-11,
b888e1ea-9739-11e4-a24e-000c29b24887:1-20
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]>

3.验证没有索引的情况

 主库创建表和插入记录

CREATE TABLE `table_index` (
  `id` int(11) NOT NULL,
  `name` varchar(20) NOT NULL,
  `age` tinyint(4) NOT NULL,
  `sex` tinyint(4) NOT NULL COMMENT '0,man,1,woman'
  ) ENGINE=InnoDB 

(dg6)root@localhost [mytest]> select * from table_index;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg6)root@localhost [mytest]>
从库看看
(dg7)root@localhost [mytest]> select * from table_index;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)
我们在从库继续搞破坏,把name为lisi的age修改为33,这时候主从已经不一致了。
(dg7)root@localhost [mytest]> select * from table_index where name='lisi';
+-----+------+-----+-----+
| id  | name | age | sex |
+-----+------+-----+-----+
| 222 | lisi |  22 |   1 |
+-----+------+-----+-----+
row in set (0.00 sec)


(dg7)root@localhost [mytest]> update table_index set age=33 where name='lisi';
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg7)root@localhost [mytest]> select * from table_index where name='lisi';
+-----+---------+-----+-----+
| id  | name    | age | sex |
+-----+---------+-----+-----+
| 222 | lisi    |  33 |   1 |
+-----+---------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]>
那么我们还是在主库更新一下记录。把lisi的age修改成30,看看从库能不能更新过来
(dg6)root@localhost [mytest]> select * from table_index where name='lisi';
+-----+------+-----+-----+
| id  | name | age | sex |
+-----+------+-----+-----+
| 222 | lisi |  22 |   1 |
+-----+------+-----+-----+
row in set (0.00 sec)

(dg6)root@localhost [mytest]>  update table_index set age=30 where name='lisi';
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg6)root@localhost [mytest]> select * from table_index where name='lisi';
+-----+------+-----+-----+
| id  | name | age | sex |
+-----+------+-----+-----+
| 222 | lisi |  30 |   1 |
+-----+------+-----+-----+
row in set (0.00 sec)

(dg6)root@localhost [mytest]>
回到从库看看,数据没有更新过来,lisi的年龄还是33,这时候主从复制也是异常的,提示1032错误(找不到记录)
(dg7)root@localhost [mytest]> select * from table_index where name='lisi';
+-----+------+-----+-----+
| id  | name | age | sex |
+-----+------+-----+-----+
| 222 | lisi |  33 |   1 |
+-----+------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 7376
               Relay_Log_File: dg7-relay-bin.000003
                Relay_Log_Pos: 724
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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 mytest.table_index; Can't find record in 'table_index', Error_code: 1032; Corrupted replication event was detected, Error_code: 1610; handler error HA_ERR_END_OF_FILE; the event's master log dg6-logbin.000001, end_log_pos 7345
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 7112
              Relay_Log_Space: 8090
              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 mytest.table_index; Can't find record in 'table_index', Error_code: 1032; Corrupted replication event was detected, Error_code: 1610; handler error HA_ERR_END_OF_FILE; the event's master log dg6-logbin.000001, end_log_pos 7345
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/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: 150425 08:30:49
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-28
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-14,
b888e1ea-9739-11e4-a24e-000c29b24887:1-27
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]>

4.验证有唯一索引情况

测试方法都一样,下面步骤我都就贴结果了。(核心思想就是,从库先修改记录,做成主从数据不一致这种情况,然后主库再更新,看看从库有没有同步主库记录)
(dg6)root@localhost [mytest]> select * from table_index;
+-----+-----+-----------+-----+-----+
| id  | sid | name      | age | sex |
+-----+-----+-----------+-----+-----+
| 111 |   1 | zhangsan  |  20 |   0 |
| 222 |   2 | lisi      |  30 |   1 |
| 333 |   3 | wangzi    |  22 |   1 |
| 444 |   4 | lilei     |  32 |   0 |
| 555 |   5 | hanmeimei |  30 |   1 |
+-----+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg6)root@localhost [mytest]> select * from table_index where sid=3;
+-----+-----+--------+-----+-----+
| id  | sid | name   | age | sex |
+-----+-----+--------+-----+-----+
| 333 |   3 | wangzi |  22 |   1 |
+-----+-----+--------+-----+-----+
row in set (0.00 sec)

(dg6)root@localhost [mytest]> update table_index set name='wangwu' where sid=3;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg6)root@localhost [mytest]> select * from table_index where sid=3;
+-----+-----+--------+-----+-----+
| id  | sid | name   | age | sex |
+-----+-----+--------+-----+-----+
| 333 |   3 | wangwu |  22 |   1 |
+-----+-----+--------+-----+-----+
row in set (0.00 sec)

(dg6)root@localhost [mytest]>
从库看看,能更新过来,而且主从复制状态是正常的
(dg7)root@localhost [mytest]> select * from table_index;
+-----+-----+-----------+-----+-----+
| id  | sid | name      | age | sex |
+-----+-----+-----------+-----+-----+
| 111 |   1 | zhangsan  |  20 |   0 |
| 222 |   2 | lisi      |  30 |   1 |
| 333 |   3 | wangzi    |  22 |   1 |
| 444 |   4 | lilei     |  32 |   0 |
| 555 |   5 | hanmeimei |  30 |   1 |
+-----+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> update table_index set name='laowang' where sid=3;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg7)root@localhost [mytest]> select * from table_index where sid=3;
+-----+-----+---------+-----+-----+
| id  | sid | name    | age | sex |
+-----+-----+---------+-----+-----+
| 333 |   3 | laowang |  22 |   1 |
+-----+-----+---------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 13038
               Relay_Log_File: dg7-relay-bin.000005
                Relay_Log_Pos: 5841
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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: 13038
              Relay_Log_Space: 6615
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-52
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-26,
b888e1ea-9739-11e4-a24e-000c29b24887:1-52
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]> select * from table_index where sid=3;
+-----+-----+--------+-----+-----+
| id  | sid | name   | age | sex |
+-----+-----+--------+-----+-----+
| 333 |   3 | wangwu |  22 |   1 |
+-----+-----+--------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 13302
               Relay_Log_File: dg7-relay-bin.000005
                Relay_Log_Pos: 6105
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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: 13302
              Relay_Log_Space: 6879
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-53
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-26,
b888e1ea-9739-11e4-a24e-000c29b24887:1-53
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]>

5.验证有主键和有普通索引情况

(dg6)root@localhost [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg6)root@localhost [mytest]> update table_key set name='zhangsir' where age=20;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg6)root@localhost [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsir  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg6)root@localhost [mytest]>
从库看看
(dg7)root@localhost [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> desc update table_key set name='xiaozhang' where age=20;
+----+-------------+-----------+-------+---------------+-----------+---------+-------+------+-------------+
| id | select_type | table     | type  | possible_keys | key       | key_len | ref   | rows | Extra       |
+----+-------------+-----------+-------+---------------+-----------+---------+-------+------+-------------+
|  1 | SIMPLE      | table_key | range | age_index     | age_index | 1       | const |    1 | Using where |
+----+-------------+-----------+-------+---------------+-----------+---------+-------+------+-------------+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> update table_key set name='xiaozhang' where age=20;
Query OK, 1 row affected (0.03 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg7)root@localhost [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | xiaozhang |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsir  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 16026
               Relay_Log_File: dg7-relay-bin.000005
                Relay_Log_Pos: 8829
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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: 16026
              Relay_Log_Space: 9603
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-63
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-28,
b888e1ea-9739-11e4-a24e-000c29b24887:1-63
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]>

6.验证只有普通索引情况

主库
CREATE TABLE `table_index` (
  `id` int(11) NOT NULL,
  `name` varchar(20) NOT NULL,
  `age` tinyint(4) NOT NULL,
  `sex` tinyint(4) NOT NULL COMMENT '0,man,1,woman',
   key age_index (`age`)
  ) ENGINE=InnoDB 
(dg6)root@localhost [mytest]>select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsir |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.00 sec)

(dg6)root@localhost [mytest]>update table_key set name='zhaoliu' where age=20;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg6)root@localhost [mytest]>select * from table_key where age=20;
+-----+---------+-----+-----+
| id  | name    | age | sex |
+-----+---------+-----+-----+
| 111 | zhaoliu |  20 |   0 |
+-----+---------+-----+-----+
row in set (0.00 sec)
从库
(dg7)root@localhost [mytest]> select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsir |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> update table_key set name='zhangsan' where age=20;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg7)root@localhost [mytest]> select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsan |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.00 sec)

(dg7)root@localhost [mytest]> select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsan |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.00 sec)
##########################提示1032错误,找不到记录

(dg7)root@localhost [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.106
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: dg6-logbin.000001
          Read_Master_Log_Pos: 16463
               Relay_Log_File: dg7-relay-bin.000005
                Relay_Log_Pos: 8993
        Relay_Master_Log_File: dg6-logbin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: No
              Replicate_Do_DB: 
          Replicate_Ignore_DB: mysql
           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 mytest.table_key; Can't find record in 'table_key', Error_code: 1032; Column 'name' cannot be null, Error_code: 1048; Column 'age' cannot be null, Error_code: 1048; Column 'sex' cannot be null, Error_code: 1048; handler error HA_ERR_END_OF_FILE; the event's master log dg6-logbin.000001, end_log_pos 16432
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 16190
              Relay_Log_Space: 10040
              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 mytest.table_key; Can't find record in 'table_key', Error_code: 1032; Column 'name' cannot be null, Error_code: 1048; Column 'age' cannot be null, Error_code: 1048; Column 'sex' cannot be null, Error_code: 1048; handler error HA_ERR_END_OF_FILE; the event's master log dg6-logbin.000001, end_log_pos 16432
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 1
                  Master_UUID: b888e1ea-9739-11e4-a24e-000c29b24887
             Master_Info_File: /data/mydata/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: 150425 09:43:27
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: b888e1ea-9739-11e4-a24e-000c29b24887:1-65
            Executed_Gtid_Set: a9926b45-975d-11e4-a339-000c29b24888:1-29,
b888e1ea-9739-11e4-a24e-000c29b24887:1-64
                Auto_Position: 1
row in set (0.00 sec)

(dg7)root@localhost [mytest]>

7.binlog格式是sbr,mbr格式的时候(PS,因为我使用了GTID,所以找了另外两台机测试)

主库

(dg1)root@127.0.0.1 [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)

(dg1)root@127.0.0.1 [mytest]> show global variables like '%binlog_format%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| binlog_format | MIXED |
+---------------+-------+
row in set (0.00 sec)

(dg1)root@127.0.0.1 [mytest]> select * from table_key;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangsan  |  20 |   0 |
| 222 | lisi      |  22 |   1 |
| 333 | wangwu    |  22 |   1 |
| 444 | lilei     |  32 |   0 |
| 555 | hanmeimei |  30 |   1 |
| 666 | lucy      |  30 |   1 |
| 777 | lili      |  30 |   1 |
| 888 | lintao    |  32 |   0 |
+-----+-----------+-----+-----+
rows in set (0.00 sec)


(dg1)root@127.0.0.1 [mytest]> update table_key set name='zhangzong' where age=20;
Query OK, 1 row affected (0.01 sec)
Rows matched: 1  Changed: 1  Warnings: 0
从库看一下
(dg2)root@127.0.0.1 [mytest]> select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsan |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.01 sec)

(dg2)root@127.0.0.1 [mytest]> update table_key set name='zhangsir' where age=20;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0

(dg2)root@127.0.0.1 [mytest]> select * from table_key where age=20;
+-----+----------+-----+-----+
| id  | name     | age | sex |
+-----+----------+-----+-----+
| 111 | zhangsir |  20 |   0 |
+-----+----------+-----+-----+
row in set (0.00 sec)

(dg2)root@127.0.0.1 [mytest]> select * from table_key where age=20;
+-----+-----------+-----+-----+
| id  | name      | age | sex |
+-----+-----------+-----+-----+
| 111 | zhangzong |  20 |   0 |
+-----+-----------+-----+-----+
row in set (0.00 sec)

(dg2)root@127.0.0.1 [mytest]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.80.101
                  Master_User: repl
                  Master_Port: 3307
                Connect_Retry: 60
              Master_Log_File: dg1.000001
          Read_Master_Log_Pos: 3340
               Relay_Log_File: mysql3307-relay-bin.000002
                Relay_Log_Pos: 3355
        Relay_Master_Log_File: dg1.000001
             Slave_IO_Running: Yes
            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: 3340
              Relay_Log_Space: 3532
              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: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 12
                  Master_UUID: fbc1bdf1-829b-11e4-9bdf-000c29b24882
             Master_Info_File: /data/3307/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: 
                Auto_Position: 0
row in set (0.00 sec)


(dg2)root@127.0.0.1


本文来自云栖社区合作伙伴“DBGEEK”


相关实践学习
如何快速连接云数据库RDS MySQL
本场景介绍如何通过阿里云数据管理服务DMS快速连接云数据库RDS MySQL,然后进行数据表的CRUD操作。
全面了解阿里云能为你做什么
阿里云在全球各地部署高效节能的绿色数据中心,利用清洁计算为万物互联的新世界提供源源不断的能源动力,目前开服的区域包括中国(华北、华东、华南、香港)、新加坡、美国(美东、美西)、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程,来了解阿里云能够为你的业务带来哪些帮助     相关的阿里云产品:云服务器ECS 云服务器 ECS(Elastic Compute Service)是一种弹性可伸缩的计算服务,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs
目录
打赏
0
0
0
0
176
分享
相关文章
ELK实现nginx、mysql、http的日志可视化实验
通过本文的步骤,你可以成功配置ELK(Elasticsearch, Logstash, Kibana)来实现nginx、mysql和http日志的可视化。通过Kibana,你可以直观地查看和分析日志数据,从而更好地监控和管理系统。希望这些步骤能帮助你在实际项目中有效地利用ELK来处理日志数据。
177 90
深入探索 BPMN、CMMN 和 DMN:从定义到应用的全方位解析
在当今快速变化的商业环境中,对象管理组织(OMG)推出了三种强大的建模标准:BPMN(业务流程模型和符号)、CMMN(案例管理模型和符号)和DMN(决策模型和符号)。它们分别适用于结构化流程管理、动态案例处理和规则驱动的决策制定,并能相互协作,覆盖更广泛的业务场景。BPMN通过直观符号绘制固定流程;CMMN灵活管理不确定的案例;DMN以表格形式定义清晰的决策规则。三者结合可优化企业效率与灵活性。 [阅读更多](https://example.com/blog)
深入探索 BPMN、CMMN 和 DMN:从定义到应用的全方位解析
Tomcat log日志解析
理解和解析Tomcat日志文件对于诊断和解决Web应用中的问题至关重要。通过分析 `catalina.out`、`localhost.log`、`localhost_access_log.*.txt`、`manager.log`和 `host-manager.log`等日志文件,可以快速定位和解决问题,确保Tomcat服务器的稳定运行。掌握这些日志解析技巧,可以显著提高运维和开发效率。
63 13
mysql的undo log、redo log、bin log、buffer pool
MySQL的undo log、redo log、bin log和buffer pool是确保数据库高效、安全和可靠运行的关键组件。理解这些组件的工作原理和作用,对于优化数据库性能和保障数据安全具有重要意义。通过适当的配置和优化,可以显著提升MySQL的运行效率和数据可靠性。
33 16
mysql的undo log、redo log、bin log、buffer pool
MySQL的undo log、redo log、bin log和buffer pool是确保数据库高效、安全和可靠运行的关键组件。理解这些组件的工作原理和作用,对于优化数据库性能和保障数据安全具有重要意义。通过适当的配置和优化,可以显著提升MySQL的运行效率和数据可靠性。
22 4
DeepSeek大模型在客服系统中的应用场景解析
在数字化浪潮下,客户服务领域正经历深刻变革,AI技术成为提升服务效能与体验的关键。DeepSeek大模型凭借自然语言处理、语音交互及多模态技术,显著优化客服流程,提升用户满意度。它通过智能问答、多轮对话引导、多模态语音客服和情绪监测等功能,革新服务模式,实现高效应答与精准分析,推动人机协作,为企业和客户创造更大价值。
95 5
淘宝拍立淘按图搜索API接口系列的应用与数据解析
淘宝拍立淘按图搜索API接口是阿里巴巴旗下淘宝平台提供的一项基于图像识别技术的创新服务。以下是对该接口系列的应用与数据解析的详细分析
DeepSeek 实践应用解析:合力亿捷智能客服迈向 “真智能” 时代
DeepSeek作为人工智能领域的创新翘楚,凭借领先的技术实力,在智能客服领域掀起变革。通过全渠道智能辅助、精准对话管理、多语言交互、智能工单处理、个性化推荐、情绪分析及反馈监控等功能,大幅提升客户服务效率和质量,助力企业实现卓越升级,推动智能化服务发展。
75 1
分片上传技术全解析:原理、优势与应用(含简单实现源码)
分片上传通过将大文件分割成多个小的片段或块,然后并行或顺序地上传这些片段,从而提高上传效率和可靠性,特别适用于大文件的上传场景,尤其是在网络环境不佳时,分片上传能有效提高上传体验。 博客不应该只有代码和解决方案,重点应该在于给出解决方案的同时分享思维模式,只有思维才能可持续地解决问题,只有思维才是真正值得学习和分享的核心要素。如果这篇博客能给您带来一点帮助,麻烦您点个赞支持一下,还可以收藏起来以备不时之需,有疑问和错误欢迎在评论区指出~
简单聊聊MySQL的三大日志(Redo Log、Binlog和Undo Log)各有什么区别
在MySQL数据库管理中,理解Redo Log(重做日志)、Binlog(二进制日志)和Undo Log(回滚日志)至关重要。Redo Log确保数据持久性和崩溃恢复;Binlog用于主从复制和数据恢复,记录逻辑操作;Undo Log支持事务的原子性和隔离性,实现回滚与MVCC。三者协同工作,保障事务ACID特性。文章还详细解析了日志写入流程及可能的异常情况,帮助深入理解数据库日志机制。

推荐镜像

更多
AI助理

你好,我是AI助理

可以解答问题、推荐解决方案等