目錄
- 01 常見故障1
- 02 常見故障2
- 03 常見故障3
- 04 常見故障4
- 05 常見問題5
- 06 常見問題6
- 07 常見問題7
- 08 常見問題8
- 09 常見問題9
MGR搭建過程中遇到的一些故障
實際中我一共部署了三套MGR環(huán)境，分別是單機多實例的MGR環(huán)境，多機同網(wǎng)段的MGR環(huán)境，多機不同網(wǎng)段的MGR環(huán)境，部署的過程大同小異，但是還是有一些有出入的地方，這里把部署過程遇到的故障列舉出來，供大家參考，如果能有幸解決您在部署時候的問題，那是極好的。
01 常見故障1
[ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: bb874065-c485-11e8-8b52-000c2934472e:1 > Group transactions: 3db33b36-0e51-409f-a61d-c99756e90155:1-11'
[ERROR] Plugin group_replication reported: 'The member contains transactions not present in the group. The member will now exit the group.'
[Note] Plugin group_replication reported: ‘To force this member into the group you can use the group_replication_allow_local_disjoint_gtids_join option'
解決方案：
根據(jù)提示打開set global group_replication_allow_local_disjoint_gtids_join=ON;
02 常見故障2
[ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: bb874065-c485-11e8-8b52-000c2934472e:1 > Group transactions: 3db33b36-0e51-409f-a61d-c99756e90155:1-15'
[Warning] Plugin group_replication reported: 'The member contains transactions not present in the group. It is only allowed to join due to group_replication_allow_local_disjoint_gtids_join option'
[Note] Plugin group_replication reported: 'This server is working as secondary member with primary member address localhost.localdomaion:3306.'
解決方案：
該故障和故障1的不同之處在于該問題出現(xiàn)時，參數(shù)group_replication_allow_local_disjoint_gtids_join已經(jīng)設置成為on了。解決該問題的方法是執(zhí)行reset master就行，然后重新在主節(jié)點和從節(jié)點開啟通道，即
CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='rpl_pass' FOR CHANNEL 'group_replication_recovery';
03 常見故障3
本機測試時，遇到下面的問題
[Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
[ERROR] Slave I/O for channel 'group_replication_recovery': error connecting to master 'rpl_user@localhost.localdomaion:' - retry-time: 60 retries: 1, Error_code: 2005
[ERROR] Plugin group_replication reported: 'There was an error when connecting to the donor server. Please check that group_replication_recovery channel credentials and all MEMBER_HOST column values of performance_schema.replication_group_members table are correct and DNS resolvable.'
[ERROR] Plugin group_replication reported: 'For details please check performance_schema.replication_connection_status table and error log messages of Slave I/O for channel group_replication_recovery.'
[Note] Plugin group_replication reported: 'Retrying group recovery connection with another donor. Attempt /'
解決方案：
這個問題是由于測試環(huán)境上三臺主機的hostname設置成為了同一個名稱，改了hostname之后，這個問題就解決了。
04 常見故障4
#在線上正式環(huán)境操作時，出現(xiàn)下面的錯誤，
mysql--root@localhost:(none) ::>>START GROUP_REPLICATION;
ERROR (HY000): The server is not configured properly to be an active member of the group. Please see more details on error log.
#查看log文件，發(fā)現(xiàn)只有一個warning：
2019-02-20T07::30.233937Z [Warning] Plugin group_replication reported: 'Group Replication requires slave-preserve-commit-order to be set to ON when using more than 1 applier threads.
解決方案：
mysql--root@localhost:(none) ::>>show variables like "%preserve%";
+--------------------------------+---------+
| Variable_name | Value |
+--------------------------------+---------+
| slave_preserve_commit_order | OFF |
+--------------------------------+---------+
row in set (0.01 sec)
mysql--root@localhost:(none) ::>>set global slave_preserve_commit_order=;
Query OK, rows affected (0.00 sec)
05 常見問題5
2019-02-20T08::31.088437Z [Warning] Plugin group_replication reported: '[GCS] Connection attempt from IP address 192.168.9.208 refused.
Address is not in the IP whitelist.'
2019-02-20T08::32.088676Z [Warning] Plugin group_replication reported: '[GCS] Connection attempt from IP address 192.168.9.208 refused.
Address is not in the IP whitelist.'
解決方法：
在my.cnf中配置group_replication_ip_whitelist參數(shù)即可解決
06 常見問題6
2019-02-20T08::44.087492Z [Warning] Plugin group_replication reported: 'read failed'
2019-02-20T08::44.096171Z [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 24801'
2019-02-20T08::14.065775Z [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group
解決方案：
將my.cnf中的參數(shù)group_replication_group_seeds設置為只包含除自身外其他group成員的ip地址以及內部通信端口，如果寫成group所有成員的IP地址，則會出現(xiàn)這個錯誤，這和相同網(wǎng)段的MGR部署方式有些差異。
07 常見問題7
[ERROR] Plugin group_replication reported: ‘[GCS] Error on opening a connection to oceanbase07: on local port: '.'
[ERROR] Plugin group_replication reported: ‘[GCS] Error on opening a connection to oceanbase08: on local port: '.'
[ERROR] Plugin group_replication reported: ‘[GCS] Error on opening a connection to oceanbase07: on local port: '.'
解決方案：
未開通防火墻上的固定端口，開通防火墻之后即可解決
08 常見問題8
[Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
[ERROR] Slave I/O for channel 'group_replication_recovery': Master command COM_REGISTER_SLAVE failed: Access denied for user 'rpl_user'@'%' (using password: YES) (Errno: 1045), Error_code: 1597
[ERROR] Slave I/O thread couldn't register on master
[Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'FIRST', position
解決方案：
漏掉了某個節(jié)點的用戶，為了保險起見，在group節(jié)點上執(zhí)行
CREATE USER rpl_user@'%';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%' IDENTIFIED BY 'rpl_pass';
09 常見問題9
[ERROR] Failed to open the relay log './localhost-relay-bin.000011' (relay_log_pos ).
[ERROR] Could not find target log file mentioned in relay log info in the index file './work_NAT_1-relay-bin. index' during relay log initialization.
[ERROR] Slave: Failed to initialize the master info structure for channel ''; its record may still be present in 'mysql.slave_master_info' table, consider deleting it.
[ERROR] Failed to open the relay log './localhost-relay-bin-group_replication_recovery.000001' (relay_log_pos ).
[ERROR] Could not find target log file mentioned in relay log info in the index file './work_NAT_1-relay-bin-group_replication_recovery.index' during relay log initialization.
[ERROR] Slave: Failed to initialize the master info structure for channel 'group_replication_recovery'; its record may still be present in 'mysql.slave_master_info' table, consider deleting it.
[ERROR] Failed to create or recover replication info repositories.
[ERROR] Slave SQL for channel '': Slave failed to initialize relay log info structure from the repository, Error_code:
[ERROR] /usr/local/mysql/bin/mysqld: Slave failed to initialize relay log info structure from the repository
[ERROR] Failed to start slave threads for channel ''
解決方案：
這個錯誤是由于slave節(jié)點由于某種原因導致找不到relay-log的位置了，需要重新reset slave
以上就是MySQL MGR搭建過程中常遇見的問題及解決辦法的詳細內容，更多關于MySQL MGR搭建的資料請關注腳本之家其它相關文章！
您可能感興趣的文章:- MySQL 8.0.15配置MGR單主多從的方法
- MySQL MGR 有哪些優(yōu)點
- mysql MGR 單主多主模式切換知識點詳解
- mysql 8.0.18 mgr 搭建及其切換功能
- MySQL 8.0.18使用clone plugin重建MGR的實現(xiàn)
- 詳解MySQL 5.7 MGR單主確定主節(jié)點方法
