mysql 中继日志_MySQL复制应用中继日志解析

最新推荐文章于 2023-01-07 15:43:35 发布
最新推荐文章于 2023-01-07 15:43:35 发布
阅读量135 收藏
点赞数
文章标签： mysql 中继日志
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_39531834/article/details/114331287
版权

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

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

20160805145815_60982.png

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”

weixin_39531834
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
MySQL数据库管理（五）日志管理、备份与恢复
ver_mouth__的博客
06-21 438
目录一：MySQL日志管理 1.1日志的分类1.1.1错误日志1.1.2通用查询日志1.1.3二进制日志1.1.4中继日志1.1.5慢查询日志1.2配置日志1.2.1修改my.cnf配置文件1.2.2重启mysql服务1.3日志的查询二：MySQL备份与恢复2.1数据备份的重要性2.2数据备份的类型2.2.1从物理与逻辑的角度，备份可分为2.2.2从数据库的备份策略角度，备份可分为2.3常见的备份方法2.3.1物理冷备2.3.2专用备份工具mydump或者mysqlhotcopy2.3.3启动二进制日志进行
MySQL日志管理详解
02-01
错误日志查询日志慢查询日志二进制日志中继日志事务日志滚动日志说明：在对应的数据目录中，以主机名+.err命名的文件，错误日志记录的信息类型：记录了服务器运行中产生的错误信息记录了服务在启动和停止是所产生的...
认真学习MySQL中的二进制日志(binlog)与中继日志（Relay log）
小小默：进无止境
01-07 3177
binlog即binary log，二进制日志文件，也叫作变更日志（update log）。它记录了数据库所有执行的DDL和DML等数据库更新事件的语句，但是不包含没有修改任何数据的语句（如数据查询语句select、show等）。 它以事件形式记录并保存在二进制文件中。通过这些信息我们可以再现数据更新操作的全过程。 >如果想要记录所有语句（例如，为了识别有问题的查询），需要使用通用查询日志。 **binlog主要应用场景：** * 一是用于数据恢复，如果MySQL数据库意外停止，可以通过二进制日志文件来
深入理解MySQL——中继日志的结构
JC的博客
07-29 1038
中继日志是连接master和slave的信息———它是复制的核心。明白如何使用中继日志，以及如何通过中继日志来协调slave线程，这点很重要。
MySQL 8 复制（六）——拓扑与性能
wzy0623的专栏
07-04 4247
目录 一、复制拓扑 1. 一主一（多）从 2. 双（多）主复制 4. 多源复制 5. Blackhole引擎与日志服务器 二、复制性能 1. 测试规划 2. sync_binlog与innodb_flush_log_at_trx_commit 3. 组提交与多线程复制 4. 基于WriteSet的多线程复制 可以在任意个主从库之间建立复杂的复制拓扑结构，如普通...
面试官：MySQL中的7种日志你都知道是干啥的吗？
xmt1139057136的专栏
03-10 3474
你知道的越多，不知道的就越多，业余的像一棵小草！你来，我们一起精进！你不来，我和你的竞争对手一起精进！编辑：业余草cnblogs.com/wy123/p/8365234.html推荐：ht...
mysql 复制原理与实践应用详解
12-14
本文实例讲述了mysql 复制原理与实践应用。分享给大家供大家参考，具体如下： 复制功能是将一个mysql数据库上的数据复到一个或多个mysql从数据库上。 复制的原理：在主服务器上执行的所有DDL和DML语句都会被记录到二...
MySQL DBA必备技能 MySQL主从复制搭建运维手册
09-18
MySQL 主从复制的原理是基于二进制日志（Binary Log）的机制。主库将改变执行事务记录着在二进制日志中，从库读取主库二进制日志更改事务记录，写入中继日志（Relay Log），然后从库读取中继日志更改记录，将变更...
MySQL六大日志详解
12-14
MySQL 中有六种日志文件， 分别是：重做日志（redo log）、回滚日志（undo log）、二进制日志（binlog）、错误日志（errorlog）、慢查询日志（slow query log）、一般查询日志（general log），中继日志（relay log...
深入解析半同步与异步的MySQL主从复制配置
12-15
简单来讲MySQL的主从复制就是一个C/S架构的应用。master可以认为是我们通常意义上所认为的server，slave可以当作是一台client。slave上的I/O线程去请求master上数据，而master验证通过slave的信息后就允许slave接入...
MySQL复制应用中继日志解析
weixin_30600197的博客
05-19 265
前言:SQL线程应用中继日志，在binlog_format是row格式的时候，是居于主键更新，下面结合一张图来证明 1.从一个大神那边得到一张图片，SQL线程应用中继日志流程，下面就实验验证一下:(PS,我个人认为这张图binlog_format为ROW格式是正确的) 2.验证有PK表情况 在主库创建表结构 CREATE TABLE `table_pk` ...
mysql中继日志_MySQL复制应用中继日志解析
weixin_42516642的博客
01-19 180
前言:SQL线程应用中继日志，在binlog_format是row格式的时候，是居于主键更新，下面结合一张图来证明1.从一个大神那边得到一张图片，SQL线程应用中继日志流程，下面就实验验证一下:(PS,我个人认为这张图binlog_format为ROW格式是正确的)2.验证有PK表情况在主库创建表结构CREATE TABLE `table_pk` (`id` int(11) NOT NULL ,...
MySQL日志之中继日志（relay log）
qazwsx_19931126的专栏
09-07 663
中继日志（relay log）
MySQL支持的日志：日志类型、二进制日志（bin log）、 中继日志
weixin_46245201的博客
03-23 1484
文章目录1. 日志类型1.1 日志的弊端2. 二进制日志（bin log）2.1 概念2.2 应用场景2.3 删除二进制文件3. 中继日志3.1 概念3.2 恢复的典型错误 1. 日志类型 慢查询日志：记录所有执行时间超过long_query_time的所有查询，方便我们对查询进行优化。 通用查询日志：记录所有连接的起始时间和终止时间，以及连接发送给数据库服务器的所有指令，对我们复原操作的实际场景、发现问题，甚至是对数据库操作的审计都有很大的帮助。 错误日志：记录MySQL服务的启动、运行或停止MySQL
mysql 测试环境过一段时间就连接不上
weiwang的专栏
05-10 4207
mysql 测试环境过一段时间就连接不上说明：测试环境是阿里云RDS mysql同步过去的用的是innobackupex恢复的，设置skip-grant-table免密码登录，版本和阿里云rds 保持一致启动方式为mysqld--defaults-file=/20180403/backup-my.cnf --user=mysql --datadir=/20180403/ &问题出现频率：频...
mysql relay log_MySQL 服务 Relay Log 中继日志说明和中继日志相关参数设置 | IT工程师的生活足迹...
weixin_42571738的博客
01-18 889
从数据库Slave服务的I/O线程从主数据库Master服务的二进制日志中读取数据库的更改记录并写入到中继日志中，然后在Slave数据库执行修改操作。这就是中继日志Relay Log。一、中继日志参数说明relay_log中继日志存储位置和文件名relay_log_info_file记录master数据库二进制日志的pos和中继日志的posmax_relay_log_size中继日志的文件最大SI...
MySQL报错端口3306解决方法
热门推荐
北纬30°
08-31 2万+
安装MySQL时候回报错一些错误，比如文件中文名，但是比较最常见的就是端口号3306的占用。 在之前的MySQL安装：https://blog.csdn.net/qq_41879385/article/details/82215828，我就有遇到过这个问题。接下来看下面。 我们在安装的时候回报如下显示，在端口号的旁边会有一个黄色的感叹号。解决办法请看下面。  这是端口号3306被占用的缘...
mysql删除中继日志_mysql 中继日志删除可以自动获取吗
weixin_30744857的博客
01-19 472
匿名用户1级2016-12-23 回答1.问题一：主从复制，中继日志不断增长，如何设置中继日志自动清除vi 配置文件my.cnf,在mysqld下增添relay_log_purge=1 (自动清除中继日志打开)重启mysql，这样SQL Thread每执行完一个events时才会判断该relay-log是否需要，已经不再需要则自动删除2.问题二：主从同步失败，如何快速同步?跳过错误，继续同步。设置...
mysql server_id作用_MySQL复制过程中server-id的理解
最新发布
06-10
在MySQL复制过程中，主服务器将变更写入二进制日志中，从服务器则从主服务器读取二进制日志，并将变更应用到自己的数据库中，从而实现数据的同步。 具体来说，当从服务器启动复制进程时，它会向主服务器发送一个...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值