社群
學習
工具庫
AI工具
休閒
搜尋
繁体中文
首頁 資料庫 mysql教程 深度理解MySQL Group Replication的RECOVERING狀態

深度理解MySQL Group Replication的RECOVERING狀態

黄舟
黄舟
Mar 22, 2017 pm 01:25 PM


接收到警報通知，db3這台群組複製成員故障down機了，等修復好，啟動伺服器，然後再啟動mysql實例，進去查看狀態，變成了RECOVERING，如下所示；

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
| CHANNEL_NAME  | MEMBER_ID  | MEMBER_HOST          | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
| group_replication_applier | 3381d155-d7d1-11e6-94f7-b8ca3af6e36c | hch_test_dbm2_121_71 |   3317 | ONLINE       |
| group_replication_applier | 664b9ce9-d7de-11e6-9e8c-18a99b763071 | hch_test_web_1_24  |        3317 | ONLINE     |
| group_replication_applier | 84dba8ff-d7d2-11e6-aa9a-18a99b76310d | bpe_service      |     3317 | RECOVERING   |
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
3 rows in set (0.00 sec)


mysql>
登入後複製

這種狀態有點類似mongodb的sendary的RECOVERING狀態，對於剛出現的MySQL Group Replication新技術，遇到這種情況，這種情況怎麼辦？

在mongodb的這種模式下，一般是secondary從primary庫上不停複製數據，所以我們遵循這種思路，去看下db2的數據目錄，看到有很多relay-bin的recovery日誌在應用執行，如下所示relay日誌包記錄

-rw-r----- 1 mysql mysql  383 1月  17 16:08 bpe_service-relay-bin-group_replication_applier.000019
-rw-r----- 1 mysql mysql  502 1月  17 16:11 bpe_service-relay-bin-group_replication_applier.000020
-rw-r----- 1 mysql mysql  502 1月  17 16:23 bpe_service-relay-bin-group_replication_applier.000021
-rw-r----- 1 mysql mysql  421 1月  17 16:23 bpe_service-relay-bin-group_replication_applier.000022
-rw-r----- 1 mysql mysql  228 1月  17 16:23 bpe_service-relay-bin-group_replication_applier.index
-rw-r----- 1 mysql mysql  312 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000007
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000008
-rw-r----- 1 mysql mysql  391 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000009
-rw-r----- 1 mysql mysql  312 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000010
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000011
-rw-r----- 1 mysql mysql  391 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000012
-rw-r----- 1 mysql mysql  312 1月  17 16:24 bpe_service-relay-bin-group_replication_recovery.000013
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000014
-rw-r----- 1 mysql mysql  391 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000015
-rw-r----- 1 mysql mysql  312 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000016
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000017
-rw-r----- 1 mysql mysql  391 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000018
-rw-r----- 1 mysql mysql  312 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000019
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000020
-rw-r----- 1 mysql mysql  391 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000021
-rw-r----- 1 mysql mysql  312 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000022
-rw-r----- 1 mysql mysql 1.1G 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000023
-rw-r----- 1 mysql mysql  391 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000024
-rw-r----- 1 mysql mysql  312 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.000025
-rw-r----- 1 mysql mysql 181M 1月  17 16:26 bpe_service-relay-bin-group_replication_recovery.000026
-rw-r----- 1 mysql mysql 1.2K 1月  17 16:25 bpe_service-relay-bin-group_replication_recovery.index
drwxr-x--- 2 mysql mysql 4.0K 1月  17 14:11 business_db
登入後複製

然後在mysql窗口，可以看到幾個線程，其中有一個就是Reading event from the relay log線程，就是表示正在應用relay日誌：

mysql> show full processlist;
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+-----------------------+
| Id | User        | Host      | db   | Command | Time | State    | Info                 |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+-----------------------+
| 28 | system user |           | NULL | Connect |  701 | Suspending    | NULL                  |
| 31 | system user |           | NULL | Connect |  701 | Slave has read all relay log; waiting for more updates | NULL  |
| 35 | system user |           | NULL | Connect |  699 | Waiting for master to send event  | NULL    |
| 36 | system user |           | NULL | Connect | 4519 | Reading event from the relay log   | NULL  |
| 38 | root        | localhost | NULL | Query   |    0 | starting   | show full processlist |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+-----------------------+
5 rows in set (0.00 sec)


mysql>
登入後複製

再過一會兒，資料同步完成之後，bpe_service就會從RECOVERING變成ONLINE狀態。這個更加證實了，數據已經同步完成。 

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID   | MEMBER_HOST          | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
| group_replication_applier | 3381d155-d7d1-11e6-94f7-b8ca3af6e36c | hch_test_dbm2_121_71 |        3317 | ONLINE       |
| group_replication_applier | 664b9ce9-d7de-11e6-9e8c-18a99b763071 | hch_test_web_1_24    |        3317 | ONLINE       |
| group_replication_applier | 84dba8ff-d7d2-11e6-aa9a-18a99b76310d | bpe_service          |        3317 | ONLINE       |
+---------------------------+--------------------------------------+----------------------+-------------+--------------+
3 rows in set (0.00 sec)


mysql>
登入後複製

去查看後台error log日誌顯示，剛開始啟動，在做CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'的時候，沒有取到值，然後看後面同步完後，就會執行加入群組複製成員的命令

“CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'.
 Previous state master_host='hch_test_web_1_24', master_port= 3317, master_log_file='', 
 master_log_pos= 4, master_bind=&#39;&#39;. New state master_host=&#39;<NULL>&#39;, master_port= 0, master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;”，
登入後複製

在執行結束後，最後告訴我們「'This server was declared online within the replication group'」已經加入了群組成員，而且變成了即時的ONLINE狀態：

2017-01-17T08:23:15.710146Z 4 [Note] Plugin group_replication reported: &#39;auto_increment_increment is reset to 1&#39;
2017-01-17T08:23:15.710200Z 4 [Note] Plugin group_replication reported: &#39;auto_increment_offset is reset to 1&#39;
2017-01-17T08:23:15.710401Z 20 [Note] Error reading relay log event for channel &#39;group_replication_applier&#39;: slave SQL thread was killed
2017-01-17T08:23:15.711212Z 17 [Note] Plugin group_replication reported: &#39;The group replication applier thread was killed&#39;
2017-01-17T08:23:42.141239Z 4 [Note] Plugin group_replication reported: &#39;Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"&#39;
2017-01-17T08:23:42.141451Z 4 [Note] Plugin group_replication reported: &#39;[GCS] Added automatically IP ranges 127.0.0.1/8,192.168.121.111/23 to the whitelist&#39;
2017-01-17T08:23:42.141990Z 4 [Note] Plugin group_replication reported: &#39;[GCS] Translated &#39;db2&#39; to 192.168.121.111&#39;
2017-01-17T08:23:42.142174Z 4 [Note] Plugin group_replication reported: &#39;[GCS] SSL was not enabled&#39;
2017-01-17T08:23:42.142220Z 4 [Note] Plugin group_replication reported: &#39;Initialized group communication with configuration: 
group_replication_group_name: "e4668cea-d7ca-11e6-86b5-18a99b76310d"; group_replication_local_address: "db2:24902"; 
group_replication_group_seeds: "db1:24901,db2:24902,db3:24903"; group_replication_bootstrap_group: false; 
group_replication_poll_spin_loops: 0; group_replication_compression_threshold: 1000000; group_replication_ip_whitelist: "AUTOMATIC"&#39;
2017-01-17T08:23:42.142936Z 28 [Note] &#39;CHANGE MASTER TO FOR CHANNEL &#39;group_replication_applier&#39; executed&#39;. 
Previous state master_host=&#39;<NULL>&#39;, master_port= 0, master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;. 
New state master_host=&#39;<NULL>&#39;, master_port= 0, master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;.

-- #（1）尝试启动默认的组复制，结果信息不对称，启动失败，然后开始初始化Group Replication
2017-01-17T08:23:42.166956Z 31 [Note] Slave SQL thread for channel &#39;group_replication_applier&#39; initialized, 
starting replication in log &#39;FIRST&#39; at position 0, relay log &#39;./bpe_service-relay-bin-group_replication_applier.000019&#39; position: 4
2017-01-17T08:23:42.166960Z 4 [Note] Plugin group_replication reported: &#39;Group Replication applier module successfully initialized!&#39;
2017-01-17T08:23:42.167064Z 4 [Note] Plugin group_replication reported: &#39;auto_increment_increment is set to 7&#39;
2017-01-17T08:23:42.167079Z 4 [Note] Plugin group_replication reported: &#39;auto_increment_offset is set to 12002&#39;
2017-01-17T08:23:42.167219Z 0 [Note] Plugin group_replication reported: &#39;state 4257 action xa_init&#39;
2017-01-17T08:23:42.167292Z 0 [Note] Plugin group_replication reported: &#39;Successfully bound to 0.0.0.0:24902 (socket=49).&#39;
2017-01-17T08:23:42.167341Z 0 [Note] Plugin group_replication reported: &#39;Successfully set listen backlog to 32 (socket=49)!&#39;
2017-01-17T08:23:42.167357Z 0 [Note] Plugin group_replication reported: &#39;Successfully unblocked socket (socket=49)!&#39;
2017-01-17T08:23:42.167400Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.167585Z 0 [Note] Plugin group_replication reported: &#39;Ready to accept incoming connections on 0.0.0.0:24902 (socket=49)!&#39;
2017-01-17T08:23:42.174427Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 50&#39;
2017-01-17T08:23:42.174807Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.175008Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 63&#39;
2017-01-17T08:23:42.175234Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.175411Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 65&#39;
2017-01-17T08:23:42.175614Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.175799Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 67&#39;
2017-01-17T08:23:42.176006Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.176176Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 69&#39;
2017-01-17T08:23:42.176377Z 0 [Note] Plugin group_replication reported: &#39;connecting to db2 24902&#39;
2017-01-17T08:23:42.176563Z 0 [Note] Plugin group_replication reported: &#39;client connected to db2 24902 fd 71&#39;
2017-01-17T08:23:42.176876Z 0 [Note] Plugin group_replication reported: &#39;connecting to db1 24901&#39;
2017-01-17T08:23:42.177312Z 0 [Note] Plugin group_replication reported: &#39;client connected to db1 24901 fd 73&#39;
2017-01-17T08:23:43.463474Z 0 [Note] Plugin group_replication reported: &#39;state 4257 action xa_snapshot&#39;
2017-01-17T08:23:43.463969Z 0 [Note] Plugin group_replication reported: &#39;new state x_recover&#39;
2017-01-17T08:23:43.464000Z 0 [Note] Plugin group_replication reported: &#39;state 4277 action xa_complete&#39;
2017-01-17T08:23:43.464275Z 0 [Note] Plugin group_replication reported: &#39;new state x_run&#39;
2017-01-17T08:23:44.619112Z 0 [Note] Plugin group_replication reported: &#39;Starting group replication recovery with view_id 14844510167669342:17&#39; 

--#（2） 开始进行组内数据recovery
2017-01-17T08:23:44.619451Z 34 [Note] Plugin group_replication reported: &#39;Establishing group recovery connection with a possible donor. Attempt 1/10&#39;
2017-01-17T08:23:44.624181Z 34 [Note] &#39;CHANGE MASTER TO FOR CHANNEL &#39;group_replication_recovery&#39; executed&#39;. Previous state master_host=&#39;<NULL>&#39;, 
master_port= 0, master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;. New state master_host=&#39;hch_test_web_1_24&#39;, master_port= 3317, 
master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;.
2017-01-17T08:23:44.628853Z 34 [Note] Plugin group_replication reported: &#39;Establishing connection to a group replication
 recovery donor 664b9ce9-d7de-11e6-9e8c-18a99b763071 at hch_test_web_1_24 port: 3317.&#39;
2017-01-17T08:23:44.629156Z 35 [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 &#39;START SLAVE Syntax&#39;
  in the MySQL Manual for more information.
2017-01-17T08:23:44.635870Z 36 [Note] Slave SQL thread for channel &#39;group_replication_recovery&#39; initialized, starting
 replication in log &#39;FIRST&#39; at position 0, relay log &#39;./bpe_service-relay-bin-group_replication_recovery.000001&#39; position: 4
2017-01-17T08:23:44.681897Z 35 [Note] Slave I/O thread for channel &#39;group_replication_recovery&#39;: 
connected to master &#39;repl@hch_test_web_1_24:3317&#39;,replication started in log &#39;FIRST&#39; at position 4
2017-01-17T08:43:34.219952Z 34 [Note] Plugin group_replication reported: &#39;Terminating existing group replication donor connection and 
purging the corresponding logs.&#39;
2017-01-17T08:43:34.220609Z 36 [Note] Slave SQL thread for channel &#39;group_replication_recovery&#39; exiting, 
replication stopped in log &#39;binlog.000042&#39; at position 185511578
2017-01-17T08:43:34.226869Z 35 [Note] Slave I/O thread killed while reading event for channel &#39;group_replication_recovery&#39;
2017-01-17T08:43:34.226886Z 35 [Note] Slave I/O thread exiting for channel &#39;group_replication_recovery&#39;, read up to log &#39;binlog.000042&#39;, position 185511578
2017-01-17T08:43:34.269973Z 34 [Note] &#39;CHANGE MASTER TO FOR CHANNEL &#39;group_replication_recovery&#39; executed&#39;. 
Previous state master_host=&#39;hch_test_web_1_24&#39;, master_port= 3317, master_log_file=&#39;&#39;,
 master_log_pos= 4, master_bind=&#39;&#39;. New state master_host=&#39;<NULL>&#39;, master_port= 0, master_log_file=&#39;&#39;, master_log_pos= 4, master_bind=&#39;&#39;.

-- # （3）已经数据恢复完成，加入组，成为组成员
2017-01-17T08:43:34.290920Z 0 [Note] Plugin group_replication reported: &#39;This server was declared online within the replication group&#39;
登入後複製

小結：mysql group replication的使用來說，有些理念比如mongodb的分片以及primary-secondary的思路理念可以參考下，這樣理解起來就會比較容易一些。

以上是深度理解MySQL Group Replication的RECOVERING狀態的詳細內容。更多資訊請關注PHP中文網其他相關文章！

本網站聲明
本文內容由網友自願投稿，版權歸原作者所有。本站不承擔相應的法律責任。如發現涉嫌抄襲或侵權的內容，請聯絡admin@php.cn

熱AI工具

Undresser.AI Undress

Undresser.AI Undress

人工智慧驅動的應用程序，用於創建逼真的裸體照片

AI Clothes Remover

AI Clothes Remover

用於從照片中去除衣服的線上人工智慧工具。

Undress AI Tool

Undress AI Tool

免費脫衣圖片

Clothoff.io

Clothoff.io

AI脫衣器

Video Face Swap

Video Face Swap

使用我們完全免費的人工智慧換臉工具，輕鬆在任何影片中換臉！

顯示更多

熱門文章

Windows 11 KB5054979中的新功能以及如何解決更新問題
3 週前 By DDD
如何修復KB5055523無法在Windows 11中安裝？
2 週前 By DDD
Inzoi：如何申請學校和大學
3 週前 By DDD
如何修復KB5055518無法在Windows 10中安裝？
2 週前 By DDD
Roblox：Dead Rails - 如何召喚和擊敗Nikola Tesla
4 週前 By 尊渡假赌尊渡假赌尊渡假赌
顯示更多

熱工具

記事本++7.3.1

記事本++7.3.1

好用且免費的程式碼編輯器

SublimeText3漢化版

SublimeText3漢化版

中文版，非常好用

禪工作室 13.0.1

禪工作室 13.0.1

強大的PHP整合開發環境

Dreamweaver CS6

Dreamweaver CS6

視覺化網頁開發工具

SublimeText3 Mac版

SublimeText3 Mac版

神級程式碼編輯軟體(SublimeText3)

顯示更多

熱門話題

gmail信箱登陸入口在哪裡
7798
15
Java教學
1644
14
CakePHP 教程
1402
52
Laravel 教程
1299
25
PHP教程
1234
29
顯示更多
Related knowledge
MySQL：世界上最受歡迎的數據庫的簡介 MySQL：世界上最受歡迎的數據庫的簡介 Apr 12, 2025 am 12:18 AM

MySQL是一種開源的關係型數據庫管理系統，主要用於快速、可靠地存儲和檢索數據。其工作原理包括客戶端請求、查詢解析、執行查詢和返回結果。使用示例包括創建表、插入和查詢數據，以及高級功能如JOIN操作。常見錯誤涉及SQL語法、數據類型和權限問題，優化建議包括使用索引、優化查詢和分錶分區。

apache怎麼連接數據庫 apache怎麼連接數據庫 Apr 13, 2025 pm 01:03 PM

Apache 連接數據庫需要以下步驟：安裝數據庫驅動程序。配置 web.xml 文件以創建連接池。創建 JDBC 數據源，指定連接設置。從 Java 代碼中使用 JDBC API 訪問數據庫，包括獲取連接、創建語句、綁定參數、執行查詢或更新以及處理結果。

MySQL的位置：數據庫和編程 MySQL的位置：數據庫和編程 Apr 13, 2025 am 12:18 AM

MySQL在數據庫和編程中的地位非常重要，它是一個開源的關係型數據庫管理系統，廣泛應用於各種應用場景。 1）MySQL提供高效的數據存儲、組織和檢索功能，支持Web、移動和企業級系統。 2）它使用客戶端-服務器架構，支持多種存儲引擎和索引優化。 3）基本用法包括創建表和插入數據，高級用法涉及多表JOIN和復雜查詢。 4）常見問題如SQL語法錯誤和性能問題可以通過EXPLAIN命令和慢查詢日誌調試。 5）性能優化方法包括合理使用索引、優化查詢和使用緩存，最佳實踐包括使用事務和PreparedStatemen

為什麼要使用mysql？利益和優勢 為什麼要使用mysql？利益和優勢 Apr 12, 2025 am 12:17 AM

選擇MySQL的原因是其性能、可靠性、易用性和社區支持。 1.MySQL提供高效的數據存儲和檢索功能，支持多種數據類型和高級查詢操作。 2.採用客戶端-服務器架構和多種存儲引擎，支持事務和查詢優化。 3.易於使用，支持多種操作系統和編程語言。 4.擁有強大的社區支持，提供豐富的資源和解決方案。

MySQL的角色：Web應用程序中的數據庫 MySQL的角色：Web應用程序中的數據庫 Apr 17, 2025 am 12:23 AM

MySQL在Web應用中的主要作用是存儲和管理數據。 1.MySQL高效處理用戶信息、產品目錄和交易記錄等數據。 2.通過SQL查詢，開發者能從數據庫提取信息生成動態內容。 3.MySQL基於客戶端-服務器模型工作，確保查詢速度可接受。

docker怎麼啟動mysql docker怎麼啟動mysql Apr 15, 2025 pm 12:09 PM

在 Docker 中啟動 MySQL 的過程包含以下步驟：拉取 MySQL 鏡像創建並啟動容器，設置根用戶密碼並映射端口驗證連接創建數據庫和用戶授予對數據庫的所有權限

laravel入門實例 laravel入門實例 Apr 18, 2025 pm 12:45 PM

Laravel 是一款 PHP 框架，用於輕鬆構建 Web 應用程序。它提供一系列強大的功能，包括：安裝： 使用 Composer 全局安裝 Laravel CLI，並在項目目錄中創建應用程序。路由： 在 routes/web.php 中定義 URL 和處理函數之間的關係。視圖： 在 resources/views 中創建視圖以呈現應用程序的界面。數據庫集成： 提供與 MySQL 等數據庫的開箱即用集成，並使用遷移來創建和修改表。模型和控制器： 模型表示數據庫實體，控制器處理 HTTP 請求。

centos7如何安裝mysql centos7如何安裝mysql Apr 14, 2025 pm 08:30 PM

優雅安裝 MySQL 的關鍵在於添加 MySQL 官方倉庫。具體步驟如下：下載 MySQL 官方 GPG 密鑰，防止釣魚攻擊。添加 MySQL 倉庫文件：rpm -Uvh https://dev.mysql.com/get/mysql80-community-release-el7-3.noarch.rpm更新 yum 倉庫緩存：yum update安裝 MySQL：yum install mysql-server啟動 MySQL 服務：systemctl start mysqld設置開機自啟動

See all articles