mysql gtid 主从复制

基于GTID环境搭建主从复制

1.环境

----------------------------------------------------------|

|mysql版本 | 5.7.14 | 5.7.14 |

|----------|----------------------------------------------|

|ip |192.168.26.233(master) | 192.168.26.75 (slave)|

|port | 3306 | 3306 |

|---------------------------------------------------------|

 

1. 主库上必须启用两个参数

gtid-mode = on

enforce-gtid-consistency = 1

log-bin = /data/mysql/mysql_3306/logs/mysql-bin

server-id = 3306100

binlog_format = row

skip_slave_start=1 数据库起来后不能直接开启复制

 

2. 查看master库的状态

mysql> show master status;

+------------------+----------+--------------+------------------+-------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+-------------------+

| mysql-bin.000020 | 154 | | | |

+------------------+----------+--------------+------------------+-------------------+

1 row in set (0.00 sec)

Executed_Gtid_Set 是空的

 

mysql> use zw

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

Database changed

mysql> show tables;

+--------------+

| Tables_in_zw |

+--------------+

| mycode |

| t1 |

+--------------+

2 rows in set (0.00 sec)

 

mysql> insert into t1 values(2);

Query OK, 1 row affected (0.00 sec)

 

mysql> show global variables like '%server%';

+---------------------------------+--------------------------------------+

| Variable_name | Value |

+---------------------------------+--------------------------------------+

| character_set_server | utf8 |

| collation_server | utf8_general_ci |

| innodb_ft_server_stopword_table | |

| server_id | 3306100 |

| server_id_bits | 32 |

| server_uuid | 7e354a2c-6f5f-11e6-997d-005056a36f08 |

+---------------------------------+--------------------------------------+

6 rows in set (0.00 sec)

server_uuid : 是 instance的唯一标识

 

3.创建一个表，插入测试数据

mysql> create table t2 (id int(6));

Query OK, 0 rows affected (0.20 sec)

 

mysql> insert into t2 values(1);

Query OK, 1 row affected (0.00 sec)

 

mysql> show master status;

+------------------+----------+--------------+------------------+------------------------------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+------------------------------------------+

| mysql-bin.000020 | 814 | | | 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 |

+------------------+----------+--------------+------------------+------------------------------------------+

1 row in set (0.00 sec)

Executed_Gtid_Set 有gtid的信息了

7e354a2c-6f5f-11e6-997d-005056a36f08

7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 后面多了个1-3,1-3就是gtid的事物信息

 

4.master端备库全库

[root@zw-test-db tmp]# mysqldump -S /tmp/mysql3306.sock -uroot -p --single-transaction --master-data=2 -A >/tmp/full_backup.sql

Enter password:

Warning: A partial dump from a server that has GTIDs will by default include the GTIDs of all transactions, even those that changed suppressed parts of the database.

If you don't want to restore GTIDs, pass --set-gtid-purged=OFF. To make a complete dump, pass --all-databases --triggers --routines --events.

会有一个警告: 大概意思是说备份里有GTID的信息，如果不需要GTID的信息，可以加上后面提示的参数过滤掉，这个警告不用管

 

备份里有gtid的信息

SET @@GLOBAL.GTID_PURGED='7e354a2c-6f5f-11e6-997d-005056a36f08:1-3';

1-3，做同步后，第4个事物会直接传过去

 

5.将master端的备份到scp到 slave端

[root@zw-test-db tmp]# scp full_backup.sql root@192.168.26.108:/tmp

 

二 、slave操作：

1.slave端的参数文件

gtid-mode = on

enforce-gtid-consistency = 1

log-bin = /data/mysql/mysql_3306/logs/mysql-bin

server-id = 3306101

binlog_format = row

skip_slave_start=1 数据库起来后不能直接开启复制

注意：server-id不能一样

 

2.重启mysql数据库

[root@llmj-svn-26-81 mysql_3306]# mysqladmin -S /tmp/mysql3306.sock -uroot -p shutdown

Enter password:

[root@llmj-svn-26-81 mysql_3306]# ps -ef|grep mysql

root 9756 9701 0 11:31 pts/2 00:00:00 grep mysq

[root@llmj-svn-26-81 mysql_3306]# mysqld --defaults-file=/data/mysql/mysql_3306/my3306.cnf &

[1] 9762

[root@llmj-svn-26-81 mysql_3306]# mysqld --defaults-file=/data/mysql/mysql_3306/my3306.cnf &

[1] 9762

 

3.恢复到 slave端

[root@llmj-svn-26-81 tmp]# mysql -S /tmp/mysql3306.sock -uroot -p < /tmp/full_backup.sql

Enter password:

[root@llmj-svn-26-81 tmp]# mysql -S /tmp/mysql3306.sock -uroot -p < /tmp/full_backup.sql

Enter password:

ERROR 1840 (HY000) at line 24: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty.

注意：多次恢复会报错，因为里面已经有gtid的信息了。

如果你还想继续强制恢复，可以在从库上 reset master ;

 

4.在slave端查看master状态

mysql> show master status;

+------------------+----------+--------------+------------------+------------------------------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+------------------------------------------+

| mysql-bin.000004 | 154 | | | 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 |

+------------------+----------+--------------+------------------+------------------------------------------+

1 row in set (0.00 sec)

mysql> show global variables like '%gtid%';

+----------------------------------+------------------------------------------+

| Variable_name | Value |

+----------------------------------+------------------------------------------+

| binlog_gtid_simple_recovery | ON |

| enforce_gtid_consistency | ON |

| gtid_executed | 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 |

| gtid_executed_compression_period | 1000 |

| gtid_mode | ON |

| gtid_owned | |

| gtid_purged | 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 |

| session_track_gtids | OFF |

+----------------------------------+------------------------------------------+

8 rows in set (0.00 sec)

 

5.reset master信息

mysql> reset master;

Query OK, 0 rows affected (0.11 sec)

mysql> show master status;

+------------------+----------+--------------+------------------+-------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+-------------------+

| mysql-bin.000001 | 154 | | | |

+------------------+----------+--------------+------------------+-------------------+

1 row in set (0.00 sec)

mysql> show global variables like '%gtid%';

+----------------------------------+-------+

| Variable_name | Value |

+----------------------------------+-------+

| binlog_gtid_simple_recovery | ON |

| enforce_gtid_consistency | ON |

| gtid_executed | |

| gtid_executed_compression_period | 1000 |

| gtid_mode | ON |

| gtid_owned | |

| gtid_purged | |

| session_track_gtids | OFF |

+----------------------------------+-------+

8 rows in set (0.01 sec)

可以看到 gtid_executed 和 gtid_purged 已经没有gtid的信息了

 

6.然后再重新恢复：

[root@llmj-svn-26-81 tmp]# mysql -S /tmp/mysql3306.sock -uroot -p < /tmp/full_backup.sql

Enter password:

然后就没有报错了，恢复成功！

 

7.然后 change master to ，这时候跟 binlog+position 有点变化

mysql> change master to master_host='192.168.26.233', master_port=3306, master_user='repl',master_password='repl', master_auto_position=1;

Query OK, 0 rows affected, 2 warnings (0.23 sec)

master_log_file='mysql-bin.000016',master_log_pos=154 这两个参数替换成了 master_auto_position=1

 

8.启动slave

mysql> start slave;

Query OK, 0 rows affected (0.01 sec)

mysql> show slave status\G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.26.233

Master_User: repl

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000020

Read_Master_Log_Pos: 814

Relay_Log_File: relay-bin.000002

Relay_Log_Pos: 414

Relay_Master_Log_File: mysql-bin.000020

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: 814

Relay_Log_Space: 655

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: 3306100

Master_UUID: 7e354a2c-6f5f-11e6-997d-005056a36f08

Master_Info_File: /data/mysql/mysql_3306/data/master.info

SQL_Delay: 0

SQL_Remaining_Delay: NULL

Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates

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: 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 状态正常！

Auto_Position: 1

Replicate_Rewrite_DB:

Channel_Name:

Master_TLS_Version:

1 row in set (0.00 sec)

ERROR:

No query specified

状态正常！

 

三、测试

1. 从库操作：

mysql> show master status;

+------------------+----------+--------------+------------------+------------------------------------------+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |

+------------------+----------+--------------+------------------+------------------------------------------+

| mysql-bin.000001 | 154 | | | 7e354a2c-6f5f-11e6-997d-005056a36f08:1-3 |

+------------------+----------+--------------+------------------+------------------------------------------+

1 row in set (0.00 sec)

 

2. 从库上操作，create table ,然后 show master status;

mysql> create table t3(id int(6));

Query OK, 0 rows affected (0.26 sec)

mysql> insert into t3 values (1);

Query OK, 1 row affected (0.00 sec)

mysql> show master status;

+-----------------+--------+-------------+----------------+---------------------------------------------------------------------------------+

| File |Position|Binlog_Do_DB |Binlog_Ignore_DB|Executed_Gtid_Set |

+-----------------+--------+-------------+----------------+---------------------------------------------------------------------------------+

| mysql-bin.000001| 564| | |7e354a2c-6f5f-11e6-997d-005056a36f08:1-3,ba0d5587-74d6-11e6-ab5c-005056a3f46e:1-2|

+-----------------+--------+-------------+----------------+---------------------------------------------------------------------------------+

1 row in set (0.00 sec)

可以看到从库的gtid的信息，也就是说从库的操作可以查出来；1-3是是主库操作的gtid,后面1-2是从库的操作的gtid

 

四、测试同步情况

1.主库操作：

mysql> use zw;

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

Database changed

mysql> select * from mycode;

+----+---------+

| id | content |

+----+---------+

| 1 | aaa |

| 2 | bbb |

| 3 | ccc |

| 4 | ddd |

| 5 | eee |

| 7 | ggg |

+----+---------+

6 rows in set (0.00 sec)

 

2.从库查看mycode表

mysql> select * from mycode;

+----+---------+

| id | content |

+----+---------+

| 1 | aaa |

| 2 | bbb |

| 3 | ccc |

| 4 | ddd |

| 5 | eee |

| 7 | ggg |

+----+---------+

6 rows in set (0.00 sec)

 

3.主库insert 一条数据

mysql> insert into mycode values(6,'fff');

Query OK, 1 row affected (0.00 sec)

mysql> select * from mycode;

+----+---------+

| id | content |

+----+---------+

| 1 | aaa |

| 2 | bbb |

| 3 | ccc |

| 4 | ddd |

| 5 | eee |

| 6 | fff |

| 7 | ggg |

+----+---------+

7 rows in set (0.00 sec)

 

4.查看从库

mysql> select * from mycode;

+----+---------+

| id | content |

+----+---------+

| 1 | aaa |

| 2 | bbb |

| 3 | ccc |

| 4 | ddd |

| 5 | eee |

| 6 | fff |

| 7 | ggg |

+----+---------+

7 rows in set (0.00 sec)

从库数据也同步过来啦！