MySQL5.7.10多元復制功能搭建

阿新 • • 發佈：2018-01-29

more 數據導入 always mysql5 uid esc 數據備份 skip repl

MySQL5.7.10多元復制功能搭建

1.環境：centos6.5
[root@mysql-m1 mysql-5.7.10]# cat /etc/redhat-release
CentOS release 6.5 (Final)
主機：

mysql-m1   192.168.56.21
mysql -m2  192.168.56.22
mysql-s    192.168.56.23

現在是mysql-m1數據庫已經搭建好，我使用自己的虛擬機進行clone 就省去多次安裝數據庫。
2.確保兩個主庫的server_id log-bin 開啟並且三個庫的server_id 不同：

[root@mysql-m1 aliyun]# sed -n ‘36,37p‘ /etc/my.cnf
log-bin = /aliyun/data/mysqllogs/bin-log/mysql-bin
server_id = 1

[root@mysql-m2 mysql-5.7.10]# sed -n ‘36,37p‘ /etc/my.cnf
log-bin = /aliyun/data/mysqllogs/bin-log/mysql-bin
server_id = 2
[root@mysql-s mysql-5.7.10]# sed -n ‘36,37p‘ /etc/my.cnf
log-bin = /aliyun/data/mysqllogs/bin-log/mysql-bin
server_id = 3

3.master上創建測試庫和表：
3.1登陸數據庫mysql-m1創建庫test01 和表h1：

[root@mysql-m1 tmp]# mysql -uroot -p -S /tmp/mysql.sock

mysql> create database test01;
Query OK, 1 row affected (0.01 sec)
mysql> use test01;
Database changed

mysql> CREATE TABLE `h1` (   `id` int(11) NOT NULL AUTO_INCREMENT,   `b1` int(11) DEFAULT NULL,   `b2` int(11) DEFAULT NULL,   `b3` int(11) GENERATED ALWAYS AS ((`b1` + `b2`)) VIRTUAL,   PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
Query OK, 0 rows affected (0.03 sec)

mysql> desc h1;
+-------+---------+------+-----+---------+-------------------+
| Field | Type    | Null | Key | Default | Extra             |
+-------+---------+------+-----+---------+-------------------+
| id    | int(11) | NO   | PRI | NULL    | auto_increment    |
| b1    | int(11) | YES  |     | NULL    |                   |
| b2    | int(11) | YES  |     | NULL    |                   |
| b3    | int(11) | YES  |     | NULL    | VIRTUAL GENERATED |
+-------+---------+------+-----+---------+-------------------+
4 rows in set (0.00 sec)

mysql> insert into h1(b1,b2) values(2,2);
Query OK, 1 row affected (0.00 sec)

mysql> select * from h1;
+----+------+------+------+
| id | b1   | b2   | b3   |
+----+------+------+------+
|  1 |    2 |    2 |    4 |
+----+------+------+------+
1 row in set (0.00 sec)

3.2登陸數據庫mysql-m2創建庫test01 和表和h2：

mysql> create database test01;
Query OK, 1 row affected (0.03 sec)

mysql>  CREATE TABLE `h2` (   `id` int(11) NOT NULL AUTO_INCREMENT,   `e1` int(11) DEFAULT NULL,   `e2` int(11) DEFAULT NULL,   `e3` int(11) GENERATED ALWAYS AS ((`e1` + `e2`)) VIRTUAL,   PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_bin;
Query OK, 0 rows affected (0.02 sec)

mysql> insert into h2(e1,e2) values(3,3);
Query OK, 1 row affected (0.06 sec)

mysql> select * from h2;
+----+------+------+------+
| id | e1   | e2   | e3   |
+----+------+------+------+
|  1 |    3 |    3 |    6 |
+----+------+------+------+
1 row in set (0.00 sec)

以下不停庫鎖表，自動切割bin-log日誌，全量備份bin-log，導入從庫中（此方法只適合5.5版本以下的數據庫備份，不適合5.7版本的數據庫備份，有待驗證）（不是這篇文檔的步驟）

[root@mysql-m1 bin-log]# mysqldump -uroot -p -S /tmp/mysql.sock --master-data=2 -A -B -R -x -F --events|gzip >/tmp/m1.sql.gz

[root@mysql-m2 mysql-5.7.10]#  mysqldump -uroot -p -S /tmp/mysql.sock --master-data=2 -A -B -R -x -F --events|gzip >/tmp/m2.sql.gz

適合5.7版本的多元同步的數據庫備份(不同的表同步到一個數據庫中):

[root@mysql-m1 tmp]#  mysqldump -uroot -p123456 --master-data=2 --single-transaction --databases  --add-drop-database  test01  >m1.sql
[root@mysql-m2 tmp]#  mysqldump -uroot -p123456 --master-data=2 --single-transaction --databases  --add-drop-database  test01  >m2.sql
[root@mysql-m1 tmp]# cat m1.sql|grep "CHANGE MASTER"
-- CHANGE MASTER TO MASTER_LOG_FILE=‘mysql-bin.000012‘, MASTER_LOG_POS=154;
[root@mysql-m2 tmp]#  cat m2.sql|grep "CHANGE MASTER"
-- CHANGE MASTER TO MASTER_LOG_FILE=‘mysql-bin.000010‘, MASTER_LOG_POS=154;

[root@mysql-m1 tmp]#  scp -rp -P22 m1.sql 192.168.56.23:/tmp/
[root@mysql-m2 tmp]#  scp -rp -P22 m2.sql 192.168.56.23:/tmp/

4.slave上操作：

[root@mysql-s tmp]# ll /tmp/
total 396
-rw-r--r--. 1 root  root  199233 May  8 01:15 m1.sql
-rw-r--r--. 1 root  root  199243 May  8 01:14 m2.sql
srwxrwxrwx. 1 mysql mysql      0 May  8 00:35 mysql.sock
-rw-------. 1 mysql mysql      5 May  8 00:35 mysql.sock.lock

[root@mysql-s tmp]# mysql -uroot -p -S /tmp/mysql.sock
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| txt001             |
+--------------------+
5 rows in set (0.06 sec)

分別在Slave上把Master_1和Master_2的數據導入Slave服務器，在導入前先修改從庫的MySQL存儲master-info和relay-info的方式，即從文件存儲改為表存儲，在my.cnf裏添加以下選擇：(註意此修改的是從庫)

[root@mysql-s tmp]# cat -n /etc/my.cnf|sed -n ‘36,39p‘
    36  log-bin = /aliyun/data/mysqllogs/bin-log/mysql-bin
    37  server_id = 1
    38  master_info_repository=TABLE
    39  relay_log_info_repository=TABLE

或者再MySQL從庫命令行操作：

[root@mysql-s ~]# mysql -uroot -p -S /tmp/mysql.sock
mysql> stop slave;
mysql> SET GLOBAL master_info_repository = ‘TABLE‘;
Query OK, 0 rows affected (0.00 sec)
mysql> SET GLOBAL relay_log_info_repository = ‘TABLE‘;
Query OK, 0 rows affected (0.00 sec)

把數據導入數據庫：
[root@mysql-s tmp]# mysql -uroot -p -S /tmp/mysql.sock </tmp/m2.sql
[root@mysql-s tmp]# mysql -uroot -p -S /tmp/mysql.sock </tmp/m1.sql

[root@mysql-s ~]# mysql -uroot -p -S /tmp/mysql.sock
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| test01             |
| txt001             |
+--------------------+
6 rows in set (0.00 sec)

mysql> use test01;
Database changed
mysql> show tables;
+------------------+
| Tables_in_test01 |
+------------------+
| h1               |
| h2               |
+------------------+
2 rows in set (0.00 sec)

mysql> select * from h1;
+----+------+------+------+
| id | b1   | b2   | b3   |
+----+------+------+------+
|  1 |    2 |    2 |    4 |
+----+------+------+------+
1 row in set (0.00 sec)

mysql> select * from h2;
+----+------+------+------+
| id | e1   | e2   | e3   |
+----+------+------+------+
|  1 |    3 |    3 |    6 |
+----+------+------+------+
1 row in set (0.00 sec)

5.在mysql-m1和mysql-m2上創建復制賬號：
這個操作跟MySQL 5.7之前版本一樣：
在mysql-m1上創建

mysql> grant replication slave on *.* to ‘rep‘@‘192.168.56.23‘ identified by ‘123456‘;
mysql> flush privileges;（必須刷新權限否則不生效的）

在mysql-m2上創建

mysql> grant replication slave on *.* to ‘rep‘@‘192.168.56.23‘ identified by ‘123456‘;
Query OK, 0 rows affected, 1 warning (0.02 sec
mysql> flush privileges; （必須刷新權限否則不生效的）

6.在slave從庫上操作進行change master :

[root@mysql-s ~]# mysql -uroot -p -S /tmp/mysql.sock
mysql> change master to MASTER_HOST=‘192.168.56.21‘ ,MASTER_USER=‘rep‘ ,MASTER_PASSWORD=‘123456‘ ,MASTER_LOG_FILE=‘mysql-bin.000012‘ ,MASTER_LOG_POS=154 FOR CHANNEL ‘mysql-m1‘;
Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql>  change master to MASTER_HOST=‘192.168.56.22‘ ,MASTER_USER=‘rep‘ ,MASTER_PASSWORD=‘123456‘ ,MASTER_LOG_FILE=‘mysql-bin.000010‘ ,MASTER_LOG_POS=154 FOR CHANNEL ‘mysql-m2‘;
Query OK, 0 rows affected, 2 warnings (0.03 sec)

mysql> start slave for CHANNEL ‘mysql-m1‘;
Query OK, 0 rows affected (0.02 sec)

mysql> start slave for CHANNEL ‘mysql-m2‘;
Query OK, 0 rows affected (0.00 sec)

mysql>

[root@mysql-s ~]# mysql -uroot -p123456 -S /tmp/mysql.sock -e "SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m1‘\G"|egrep "Slave_IO_Running|Slave_SQL_Running"
mysql: [Warning] Using a password on the command line interface can be insecure.
Slave_IO_Running: Connecting (報錯) 此處為yes才是正常的
Slave_SQL_Running: Yes
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
7.同步報錯解決方法:

7.1.看錯誤日誌:
[root@mysql-s ~]# cat /aliyun/data/mysql/mysql_3306.err

7.2.檢查防火墻是否關閉:
（從庫本地和主庫本地的防火墻）

[root@mysql-s ~]# mysql -urep -p123456 -h192.168.56.21
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can‘t connect to MySQL server on ‘192.168.56.21‘ (113)

[root@mysql-s ~]# mysql -urep -p123456 -h192.168.56.22
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2003 (HY000): Can‘t connect to MySQL server on ‘192.168.56.22‘ (113)

[root@mysql-s ~]# /etc/init.d/iptables stop
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Unloading modules:   
[root@mysql-m1 tmp]# /etc/init.d/iptables stop
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Unloading modules:  

[root@mysql-m2 tmp]# /etc/init.d/iptables stop
iptables: Setting chains to policy ACCEPT: filter          [  OK  ]
iptables: Flushing firewall rules:                         [  OK  ]
iptables: Unloading modules:                               [  OK  ]
[root@mysql-m2 tmp]#

7.3. 修改/ect/my.cnf中server_id 未生效:

[root@mysql-s ~]# mysql -urep -p123456 -h192.168.56.21 成功連接
但是從庫連接mysql-m1還是報錯：
但是從庫連接mysql-m2還是報錯：

[root@mysql-s ~]# mysql -uroot -p123456 -S /tmp/mysql.sock -e "SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m1‘\G"|egrep  "Slave_IO_Running|Slave_SQL_Running|Last_IO_Error"
mysql: [Warning] Using a password on the command line interface can be insecure.
             Slave_IO_Running: No
            Slave_SQL_Running: Yes
                Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this does not always make sense; please check the manual before using it).
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
      Last_IO_Error_Timestamp: 160508 03:03:05

原因是/ect/my.cnf 配置文件中修改server_id時。沒有重啟服務，所以修改沒有生效
[root@mysql-s mysql-5.7.10]# cd /aliyun/server/mysql-5.7.10/
pkill mysqld
[root@mysql-s mysql-5.7.10]# sh start_mysql.sh
三個數據庫都同樣操作

7.4.但是還是報錯:

 [root@mysql-s ~]# mysql -uroot -p123456 -S /tmp/mysql.sock -e "SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m1‘\G"|egrep  "Slave_IO_Running|Slave_SQL_Running|Last_IO_Error"
mysql: [Warning] Using a password on the command line interface can be insecure.
             Slave_IO_Running: No
            Slave_SQL_Running: Yes
                Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs; these UUIDs must be different for replication to work.
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
      Last_IO_Error_Timestamp: 160508 03:23:36

原因是mysql-s 虛擬機是基於mysql-m1的虛擬機克隆過來的，mysqlm1上的文件auto.cnf和mysql-s /mysql=m2上文件的auto.cnf 是一樣的，所以報錯

[root@mysql-s mysql]# cat /aliyun/data/mysql/auto.cnf 
[auto]
server-uuid=3652e06e-1467-11e6-ab9f-000c2970db66

[root@mysql-m1 mysql-5.7.10]# cat /aliyun/data/mysql/auto.cnf 
[auto]
server-uuid=3652e06e-1467-11e6-ab9f-000c2970db66
[root@mysql-m2 mysql-5.7.10]# cat /aliyun/data/mysql/auto.cnf 
[auto]
server-uuid=3652e06e-1467-11e6-ab9f-000c2970db66
把這三個auto.cnf文件中的數值改成隨便不一樣的就行。然後依次重啟數據庫，就好了

[root@mysql-s mysql-5.7.10]# mysql -uroot -p123456 -S /tmp/mysql.sock -e "SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m1‘\G"|egrep  "Slave_IO_Running|Slave_SQL_Running|Last_IO_Error"
mysql: [Warning] Using a password on the command line interface can be insecure.
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
                Last_IO_Error: 
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
      Last_IO_Error_Timestamp:

可以通過查看performance_schema相關的表查看同步狀態，執行命令：

mysql> SELECT * FROM performance_schema.replication_connection_status;
監控復制狀態
+--------------+------------+--------------------------------------+-----------+---------------+---------------------------+--------------------------+--------------------------+-------------------+--------------------+----------------------+
| CHANNEL_NAME | GROUP_NAME | SOURCE_UUID                          | THREAD_ID | SERVICE_STATE | COUNT_RECEIVED_HEARTBEATS | LAST_HEARTBEAT_TIMESTAMP | RECEIVED_TRANSACTION_SET | LAST_ERROR_NUMBER | LAST_ERROR_MESSAGE | LAST_ERROR_TIMESTAMP |
+--------------+------------+--------------------------------------+-----------+---------------+---------------------------+--------------------------+--------------------------+-------------------+--------------------+----------------------+
| mysql-m1     |            | 3652e06e-1467-11e1-ab9f-000c2970db66 |      NULL | OFF           |                        37 | 2016-05-08 04:26:38      |                          |                 0 |                    | 0000-00-00 00:00:00  |
| mysql-m2     |            | 3652e06e-1467-11e6-ab9f-000c2970db66 |        41 | ON            |                        47 | 2016-05-08 04:51:32      |                          |                 0 |                    | 0000-00-00 00:00:00  |
+--------------
+------------+--------------------------------------+-----------+---------------+---------------------------+--------------------------+--------------------------+-------------------+--------------------+----------------------+

mysql> stop slave;(停止時必須同時開啟各個slave，否則不能同步)

Query OK, 0 rows affected (0.01 sec)

mysql> set global sql_slave_skip_counter=10;
mysql> start slave for CHANNEL ‘mysql-m1‘;
mysql> start slave for CHANNEL ‘mysql-m2‘;
mysql> SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m1‘\G
mysql> SHOW SLAVE STATUS FOR CHANNEL ‘mysql-m2‘\G

8.MySQL 5.7的多源復制用處：
8.1、MySQL 5.7的多源復制，能有效的解決分庫分表的數據統計問題，同時也可以實現在一臺從服務器對多臺主服務器的數據備份。

8.2、MySQL 5.7的多源復制的出現，我們就不需要使用MariaDB 的多主一從的架構了，讓很多小夥伴又看到了新的希望。
參考資料：

http://dev.mysql.com/doc/refman/5.7/en/change-master-to.html
http://www.longlong.asia/2015/10/21/mysql57-new-features.html

MySQL-5.7文檔看考資料：
http://www.cnblogs.com/xuanzhi201111/p/5148113.html
mysql多元復制資料地址
http://www.mamicode.com/info-detail-1189601.html
mysql 數據庫5.7編譯安裝
http://www.cnblogs.com/xuanzhi201111/p/5148113.html
http://www.mamicode.com/info-detail-1189601.html
http://huqiji.iteye.com/blog/2068613

MySQL5.7.10多元復制功能搭建

more 數據導入 always mysql5 uid esc 數據備份 skip repl MySQL5.7.10多元復制功能搭建 1.環境：centos6.5[root@mysql-m1 mysql-5.7.10]# cat /etc/redhat-release Ce

MySQL5.7.10多元復制功能搭建

MySQL5.7.10多元復制功能搭建

MySQL5.7--------基於無損復制搭建主從

MySQL5.7多源復制

MySQL5.7.16 gtid復制

Mysql5.7 ssl主從復制

Mysql5.7多源復制，過濾復制一段時間後增加復制一個庫的實現方法

MySQL5.7 半同步復制

MySQL 5.7 延遲復制環境搭建和測試

Centos7.5安裝mysql5.7.24二進制包方式部署(keepalived+主從復制)

Centos7.5安裝mysql5.7.24二進制包方式部署(主從復制)

Linux下MySQL5.7.18二進制包安裝（無默認配置文件my_default.cnf）

mysql-學習-10-20170531-復制類型的選擇

MySQL 5.7下主從復制延遲解決方案

MySQL master-slave主從復制環境搭建初試

fread/fwrite實現復制功能

js插件實現一鍵復制功能

MySQL 5.7並發復制和mysqldump相互阻塞引起的復制延遲

微信小程序的文字復制功能如何實現？

Linux服務器部署mysql5.7.x 二進制包

原生js實現點擊復制功能

MySQL5.7.10多元復制功能搭建

相關推薦