1. 程式人生 > >Mysql Group Replication 簡介及單主模式組復制配置【轉】

Mysql Group Replication 簡介及單主模式組復制配置【轉】

ror ipv4 mysql命令 value tail force action dmi where

一 Mysql Group Replication簡介 Mysql Group Replication(MGR)是一個全新的高可用和高擴張的MySQL集群服務。 高一致性,基於原生復制及paxos協議的組復制技術,以插件方式提供一致數據安全保證; 高容錯性,大多數服務正常就可繼續工作,自動不同節點檢測資源征用沖突,按順序優先處理,內置自動防腦裂機制; 高擴展性,自動添加移除節點,並更新組信息; 高靈活性,單主模式和多主模式。單主模式自動選主,所有更新操作在主進行;多主模式,所有server同時更新。 二 Mysql Group Replication與傳統復制的區別和大幅改進 1.傳統復制 主-從復制:有一個主和不等數量的從。主節點執行的事務會異步發送給從節點,在從節點重新執行。(異步和半同步) (半同步相對異步Master會確認Slave是否接到數據,更加安全) 技術分享
技術分享 (原理見主從復制筆記) 2.並行復制 技術分享 並行復制:復制->廣播->正式復制 優勢: 彈性復制(高擴展性):server動態添加移除 高可用分片(高擴展性):分片實現寫擴展,每個分片是一個復制組。 替代主從復制(高擴展性):整組寫入,避免單點爭用。 自動化系統:自動化部署Mysql復制到已有復制協議的自動化系統。 故障檢測與容錯:自動檢測,若服務faild,組內成員大多數達成認為該服務已不正常,則自動隔離。 組內成員會構成一個視圖,組內成員主動加入或離開(主動或被動),都會更新組配置,更新視圖。成員自願離開,先更新組配置,然後采用大多數成員(不包含主動脫離的成員)意見是否確認該成員離開更新視圖。如果是故障要排除,則需大多數服務確認(包括故障成員意見),然後才會更新組配置和視圖。 最大允許即時故障數:f=(n-1)/2,多數正常則正常 三 主從復制限制

1.存儲引擎必須為innodb

2.每個表必須提供主鍵

3.只支持ipv4,網絡需求較高

4.一個group最多只能有9臺服務器

5.不支持Replication event checksums,

6.不支持Savepoints

7.multi-primary mode部署方式不支持SERIALIZABLE事務隔離級別

8.multi-primary mode部署方式不能完全支持級聯外鍵約束

9.multi-primary mode部署方式不支持在不同節點上對同一個數據庫對象並發執行DDL(在不同節點上對同一行並發進行RW事務,後發起的事務會失敗)
四 單主模式布置組復制 (組中server可在獨立物理機運行,也可在同一臺機器,同一機器采用多實例,也就是邏輯認為是獨立機器)
技術分享 1.安裝mysql5.7包 1.卸載系統已有數據庫
#檢測系統是否已安裝mariadb,如有則卸載
rpm -qa | grep mariadb
rpm -e mariadb-libs --nodeps

2.編譯安裝mysql5.7
#添加mysql用戶組並添加mysql用戶(不允許登錄)
groupadd mysql
useradd -r -g mysql -s /bin/false -M mysql
#下載mysql源碼包
wget https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-5.7.17.tar.gz
#安裝編譯工具和依賴包
yum install -y cmake make gcc gcc-c++
yum install -y ncurses-devel openssl-devel bison-devel libaio libaio-devel
# boost庫安裝
# 該步驟可以省略,在cmake階段添加參數-DDOWNLOAD_BOOST=1 -DWITH_BOOST=/usr/local/boost即可
wget http://sourceforge.net/projects/boost/files/boost/1.59.0/boost_1_59_0.tar.gz
tar -zxvf boost_1_59_0.tar.gz -C /usr/local
mv /usr/local/boost_1_59_0 /usr/local/boost
cd /usr/local/boost
./bootstrap.sh
./b2 stage threading=multi link=shared
./b2 install threading=multi link=shared
#安裝編譯mysql
cd
tar -zxvf mysql-5.7.17.tar.gz
cd mysql-5.7.17
#使用cmake工具設置參數,新版的php都從configure改用cmake
cmake -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DMYSQL_DATADTR=/usr/local/mysql/data -DSYSCONFDIR=/etc -DMYSQL_USER=mysql -DWITH_MYISAM_STORAGE_ENGINE=1 -DWITH_INNOBASE_STORAGE_ENGINE=1 -DWITH_ARCHIVE_STORAGE_ENGINE=1 -DWITH_MEMORY_STORAGE_ENGINE=1 -DWITH_READLINE=1 -DMYSQL_UNIX_ADDR=/usr/local/mysql/mysql.sock -DMYSQL_TCP_PORT=3306 -DENABLED_LOCAL_INFILE=1 -DENABLE_DOWNLOADS=1 -DWITH_PARTRTION_STORAGE_ENGINE=1 -DEXTRA_CHARSETS=all -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci -DWITH_DEBUG=0 -DMYSQL_MAINTAINER_MODE=0 -DMITH_SSL:STRING=bundled -DWITH_ZLIB:STRING=bundled -DDOWNLOAD_BOOST=1 -DWITH_BOOST=/usr/local/boost
make && make install
#默認1個線程編譯,可使用指定線程數加快編譯
#make -j $(grep processor /proc/cpuinfo | wc -l) && make install
#將mysql目錄權限給mysql用戶
chown -Rf mysql:mysql /usr/local/mysql
#設置mysql的默認配置文件
cp /usr/local/mysql/support-files/my-default.cnf /etc/my.cnf
#把mysql命令加入查找路徑
echo "export PATH=$PATH:/usr/local/mysql/bin" >>/etc/profile
source /etc/profile

防火墻和selinux設置
firewall-cmd --permanent --add-port=3307/tcp
firewall-cmd --permanent --add-port=3308/tcp
firewall-cmd --permanent --add-port=3309/tcp
firewall-cmd --permanent --add-port=3407/tcp
firewall-cmd --permanent --add-port=3408/tcp
firewall-cmd --permanent --add-port=3409/tcp
firewall-cmd --reload
setenforce 0
sed -i s#enforcing#permissive#g /etc/selinux/config

3.部署組復制實例
mkdir /data
#初始化數據庫,創建數據庫
mysqld --initialize-insecure --user=mysql --basedir=/usr/local/mysql --datadir=/data/s1
mysqld --initialize-insecure --user=mysql --basedir=/usr/local/mysql --datadir=/data/s2
mysqld --initialize-insecure --user=mysql --basedir=/usr/local/mysql --datadir=/data/s3

4.配置組復制實例S1
cat > /data/s1/my.cnf <<EOF
[mysqld]
# server configuration
user=mysql
datadir=/data/s1
basedir=/usr/local/mysql/
port=3307
socket=/usr/local/mysql/s1.sock
#復制框架
server_id=1
gtid_mode=ON
enforce_gtid_consistency=ON
master_info_repository=TABLE
relay_log_info_repository=TABLE
binlog_checksum=NONE
log_slave_updates=ON
log_bin=binlog
binlog_format=ROW
#組復制設置
#server必須為每個事務收集寫集合,並使用XXHASH64哈希算法將其編碼為散列
transaction_write_set_extraction=XXHASH64
#告知插件加入或創建組命名,UUID
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
#server啟動時不自啟組復制
loose-group_replication_start_on_boot=off
#告訴插件使用IP地址,端口3407用於接收組中其他成員轉入連接
loose-group_replication_local_address="127.0.0.1:3407"
#啟動組server,種子server,加入組應該連接這些的ip和端口;其他server要加入組得由組成員同意
loose-group_replication_group_seeds="127.0.0.1:3407,127.0.0.1:3408,127.0.0.1:3409"
loose-group_replication_bootstrap_group=off
loose-group_replication_single_primary_mode=FALSE
loose-group_replication_enforce_update_everywhere_checks= TRUE
EOF

5.用戶憑據
#啟動mysql實例1服務
nohup mysqld --defaults-file=/data/s1/my.cnf >/data/s1/nohup.out 2>/data/s1/nohup.out &
#登錄mysql s1
mysql -uroot -h127.0.0.1 -P3307 --skip-password
#修改root密碼
alter user root@localhost identified by 123456;
#下面操縱不寫入二進制日誌,避免修改傳遞給其他實例,先關閉
set sql_log_bin=0;
#創建擁有replication slave權限mysql用戶
create user [email protected]%;
grant replication slave on *.* to [email protected]% identified by rpl_pass;
flush privileges;
#開啟二進制寫入
set sql_log_bin=1;
#分布式恢復加入組的server執行第一步
#change master to語言將server配置為,在下次需要從其他成員恢復狀態時,使用group_replication_recovery復制通道的給定憑證。
change master to master_user=rpl_user,master_password=rpl_pass for channel group_replication_recovery;
#建議每個mysql通過配置唯一主機名,通過DNS或本地設置。(相同可能導致無法恢復)

6.啟動組復制
#安裝組復制插件
install plugin group_replication soname group_replication.so;
#檢測插件是否安裝成功
show plugins;
+----------------------------+----------+--------------------+----------------------+---------+ | Name | Status | Type | Library | License | +----------------------------+----------+--------------------+----------------------+---------+ ...... | group_replication | ACTIVE | GROUP REPLICATION | group_replication.so | GPL | +----------------------------+----------+--------------------+----------------------+---------+
#server s1引導組,啟動組復制程序(復制組只啟動一次就行)
set global group_replication_bootstrap_group=ON;
start group_replication;
set global group_replication_bootstrap_group=OFF;
#檢測組是否創建並已加入新成員
select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+ | CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | +---------------------------+--------------------------------------+-------------+-------------+--------------+ | group_replication_applier | 70bf7af3-1657-11e7-82a8-000c29433013 | test1 | 3307 | ONLINE | +---------------------------+--------------------------------------+-------------+-------------+--------------+

7.測試
mysql> create database test;
2017-03-31T23:23:45.535115Z 8 [Note] Plugin group_replication reported: Primary had applied all relay logs, disabled conflict detection
Query OK, 1 row affected (0.03 sec)
mysql> use test;
Database changed
mysql> create table t1(c1 int primary key,c2 text not null);
Query OK, 0 rows affected (0.03 sec)
mysql> insert into t1 values (1 , Luis);
Query OK, 1 row affected (0.01 sec)
mysql> select * from t1;
+----+------+
| c1 | c2 |
+----+------+
| 1 | Luis |
+----+------+
1 row in set (0.00 sec)
mysql> show binlog events;
+---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+
| Log_name | Pos | Event_type | Server_id | End_log_pos | Info | +---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+ | binlog.000001 | 4 | Format_desc | 1 | 123 | Server ver: 5.7.17-log, Binlog ver: 4 | | binlog.000001 | 123 | Previous_gtids | 1 | 150 | | | binlog.000001 | 150 | Gtid | 1 | 211 | SET @@SESSION.GTID_NEXT= 21355e09-16ea-11e7-bb6b-000c29433013:1 | | binlog.000001 | 211 | Query | 1 | 386 | ALTER USER root@localhost IDENTIFIED WITH mysql_native_password AS *6BB4837EB74329105EE4568DDA7DC67ED2CA2AD9 | | binlog.000001 | 386 | Gtid | 1 | 447 | SET @@SESSION.GTID_NEXT= aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1 | | binlog.000001 | 447 | Query | 1 | 506 | BEGIN | | binlog.000001 | 506 | View_change | 1 | 645 | view_id=14910585094598745:1 | | binlog.000001 | 645 | Query | 1 | 710 | COMMIT | | binlog.000001 | 710 | Gtid | 1 | 771 | SET @@SESSION.GTID_NEXT= aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:2 | | binlog.000001 | 771 | Query          | 1 | 861 | create database test | | binlog.000001 | 861 | Gtid | 1 | 922 | SET @@SESSION.GTID_NEXT= aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:3 | | binlog.000001 | 922 | Query |         1 | 1044 | use `test`; create table t1(c1 int primary key,c2 text not null) | | binlog.000001 | 1044 | Gtid | 1 | 1105 | SET @@SESSION.GTID_NEXT= aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:4 | | binlog.000001 | 1105 | Query | 1 | 1173 | BEGIN | | binlog.000001 | 1173 | Table_map | 1 | 1216 | table_id: 220 (test.t1) | | binlog.000001 | 1216 | Write_rows | 1 | 1258 | table_id: 220 flags: STMT_END_F | | binlog.000001 | 1258 | Xid | 1 | 1285 | COMMIT /* xid=40 */ | +---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+ 17 rows in set (0.00 sec)

8.第二個實例添加(S2)
cat > /data/s2/my.cnf <<EOF
[mysqld]
# server configuration
user=mysql
datadir=/data/s2
basedir=/usr/local/mysql/
port=3308
socket=/usr/local/mysql/s2.sock
#復制框架
server_id=2
gtid_mode=ON
enforce_gtid_consistency=ON
master_info_repository=TABLE
relay_log_info_repository=TABLE
binlog_checksum=NONE
log_slave_updates=ON
log_bin=binlog
binlog_format=ROW
#組復制設置
#server必須為每個事務收集寫集合,並使用XXHASH64哈希算法將其編碼為散列
transaction_write_set_extraction=XXHASH64
#告知插件加入或創建組命名,UUID
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
#server啟動時不自啟組復制
loose-group_replication_start_on_boot=off
#告訴插件使用IP地址,端口3408用於接收組中其他成員轉入連接
loose-group_replication_local_address="127.0.0.1:3408"
#啟動組server,種子server,加入組應該連接這些的ip和端口;其他server要加入組得由組成員同意
loose-group_replication_group_seeds="127.0.0.1:3407,127.0.0.1:3408,127.0.0.1:3409"
loose-group_replication_bootstrap_group=off
loose-group_replication_single_primary_mode=FALSE
loose-group_replication_enforce_update_everywhere_checks= TRUE
EOF

9.用戶憑證(S2)
#啟動mysql實例2服務
nohup mysqld --defaults-file=/data/s2/my.cnf >/data/s2/nohup.out 2>/data/s2/nohup.out &
#登錄mysql s1
mysql -uroot -h127.0.0.1 -P3308 --skip-password
#修改root密碼
alter user root@localhost identified by 123456;
#下面操縱不寫入二進制日誌,避免修改傳遞給其他實例,先關閉
set sql_log_bin=0;
#創建擁有replication slave權限mysql用戶
create user [email protected]%;
grant replication slave on *.* to [email protected]% identified by rpl_pass;
flush privileges;
#開啟二進制寫入
set sql_log_bin=1;
#分布式恢復加入組的server執行第一步
#change master to語言將server配置為,在下次需要從其他成員恢復狀態時,使用group_replication_recovery復制通道的給定憑證。
change master to master_user=rpl_user,master_password=rpl_pass for channel group_replication_recovery;
#建議每個mysql通過配置唯一主機名,通過DNS或本地設置。(相同可能導致無法恢復)

10.添加組
#安裝組復制插件
install plugin group_replication soname group_replication.so;
#檢測插件是否安裝成功
show plugins;
+----------------------------+----------+--------------------+----------------------+---------+ | Name | Status | Type | Library | License | +----------------------------+----------+--------------------+----------------------+---------+ ...... | group_replication | ACTIVE | GROUP REPLICATION | group_replication.so | GPL | +----------------------------+----------+--------------------+----------------------+---------+
#添加到復制組(不用再設置啟動,該組已在是s1時啟動)
set global group_replication_allow_local_disjoint_gtids_join=ON;
start group_replication;
#檢測組是否創建並已加入新成員
select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+ | CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE | +---------------------------+--------------------------------------+-------------+-------------+--------------+ | group_replication_applier | 21355e09-16ea-11e7-bb6b-000c29433013 | test1 | 3307 | ONLINE       | | group_replication_applier | 25b39bc8-16ea-11e7-bc1e-000c29433013 | test1 | 3308 | ONLINE | +---------------------------+--------------------------------------+-------------+-------------+--------------+
   11.測試同步是否正常
mysql> show databases like test;
+-----------------+
| Database (test) |
+-----------------+
| test |
+-----------------+

問題: #在建立第二個mysql實例s2時,會有以下現象,s2一直處於RECOVERING狀態。
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 21355e09-16ea-11e7-bb6b-000c29433013 | test1 | 3307 | ONLINE |
| group_replication_applier | 25b39bc8-16ea-11e7-bc1e-000c29433013 | test1 | 3308 | RECOVERING |
+---------------------------+--------------------------------------+-------------+-------------+--------------+

錯誤日誌如下:
[ERROR] Slave I/O for channel group_replication_recovery: error connecting to master [email protected]:3307 - retry-time: 60 retries: 1, Error_code: 2003
[ERROR] Plugin group_replication reported: There was an error when connecting to the donor server. Check group replication recoverys connection credentials.

原因:mysql組復制用的是域名連接,我的主機設置名字為test1,但沒有在hosts文件中聲明其IP為127.0.0.1。(DNS就更沒有了)導致s2無法正常訪問s1。因而報錯。 解決方法:修改/etc/hosts文件,追加127.0.0.1 對應主機名為test1。然後重新啟動組復制就可以。 參考博客 http://wangwei007.blog.51cto.com/680.19/1907145 《Mysql Group Repaliation》京東翻譯 參考博客 http://www.voidcn.com/blog/d6619309/article/p-6346153.html 轉自 http://blog.csdn.net/hzsunshine/article/details/69132225

Mysql Group Replication 簡介及單主模式組復制配置【轉】