MySQL复制应用中继日志解析
Posted woqutechteam
tags:
篇首语：本文由小常识网(cha138.com)小编为大家整理，主要介绍了MySQL复制应用中继日志解析相关的知识，希望对你有一定的参考价值。
作者 ：沃趣科技高级数据库专家 邱文辉
1.从一个大神那边得到一张图片，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 | +-----+-----------+-----+-----+ 5 rows in set (0.00 sec) (dg6)root@localhost [mytest]> show global variables like '%binlog_format%'; +---------------+-------+ | Variable_name | Value | +---------------+-------+ | binlog_format | ROW | +---------------+-------+ 1 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 | +-----+-----------+-----+-----+ 5 rows in set (0.00 sec) (dg7)root@localhost [mytest]> show global variables like '%binlog_format%'; +--------------------------+-------------------+ | Variable_name | Value | +--------------------------+-------------------+ | binlog_format | ROW | +--------------------------+-------------------+ 8 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 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 | +-----+-----------+-----+-----+ 5 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 | +-----+--------+-----+-----+ 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 | +-----+---------+-----+-----+ 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 | +-----+--------+-----+-----+ 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 | +-----+---------+-----+-----+ 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 | +-----+--------+-----+-----+ 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 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 | +-----+-----------+-----+-----+ 5 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 | +-----+-----------+-----+-----+ 5 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 |
+-----+------+-----+-----+
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 | +-----+---------+-----+-----+ 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 | +-----+------+-----+-----+ 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 | +-----+------+-----+-----+ 1 row in set (MySQL5.7主从复制