アラーム通知を受信しました。db3 グループのレプリケーション メンバーがダウンしています。修復されるまで待ってから、サーバーを起動し、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 グループ レプリケーション テクノロジでは、この状況が発生した場合はどうすればよいでしょうか。
このモードの mongodb では、通常、セカンダリはプライマリ ライブラリからデータをコピーします。そのため、この考えに従い、db2 データ ディレクトリを調べて、大量の relay-bin リカバリ ログを確認します アプリケーションが実行されると、リレー ログ パッケージは以下のように記録されます
-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 ウィンドウにいくつかのスレッドが表示されます。そのうちの 1 つはリレー ログからの読み取りイベント スレッドで、リレー ログが適用されていることを意味します。
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>
バックグラウンド エラー ログを確認してください。 CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' が実行されました' を実行すると、同期が完了した後、グループに参加したことがわかります。レプリケーション メンバー コマンド
“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=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''”，
が実行されると、最終的に「このサーバーはレプリケーション グループ内でオンラインとして宣言されました」がグループ メンバーに追加され、リアルタイム ONLINE ステータスになったことがわかります。
2017-01-17T08:23:15.710146Z 4 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1' 2017-01-17T08:23:15.710200Z 4 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1' 2017-01-17T08:23:15.710401Z 20 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed 2017-01-17T08:23:15.711212Z 17 [Note] Plugin group_replication reported: 'The group replication applier thread was killed' 2017-01-17T08:23:42.141239Z 4 [Note] Plugin group_replication reported: 'Group communication SSL configuration: group_replication_ssl_mode: "DISABLED"' 2017-01-17T08:23:42.141451Z 4 [Note] Plugin group_replication reported: '[GCS] Added automatically IP ranges 127.0.0.1/8,192.168.121.111/23 to the whitelist' 2017-01-17T08:23:42.141990Z 4 [Note] Plugin group_replication reported: '[GCS] Translated 'db2' to 192.168.121.111' 2017-01-17T08:23:42.142174Z 4 [Note] Plugin group_replication reported: '[GCS] SSL was not enabled' 2017-01-17T08:23:42.142220Z 4 [Note] Plugin group_replication reported: '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"' 2017-01-17T08:23:42.142936Z 28 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_applier' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. -- #（1）尝试启动默认的组复制，结果信息不对称，启动失败，然后开始初始化Group Replication 2017-01-17T08:23:42.166956Z 31 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './bpe_service-relay-bin-group_replication_applier.000019' position: 4 2017-01-17T08:23:42.166960Z 4 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!' 2017-01-17T08:23:42.167064Z 4 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7' 2017-01-17T08:23:42.167079Z 4 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 12002' 2017-01-17T08:23:42.167219Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_init' 2017-01-17T08:23:42.167292Z 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:24902 (socket=49).' 2017-01-17T08:23:42.167341Z 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=49)!' 2017-01-17T08:23:42.167357Z 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=49)!' 2017-01-17T08:23:42.167400Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.167585Z 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:24902 (socket=49)!' 2017-01-17T08:23:42.174427Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 50' 2017-01-17T08:23:42.174807Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.175008Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 63' 2017-01-17T08:23:42.175234Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.175411Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 65' 2017-01-17T08:23:42.175614Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.175799Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 67' 2017-01-17T08:23:42.176006Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.176176Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 69' 2017-01-17T08:23:42.176377Z 0 [Note] Plugin group_replication reported: 'connecting to db2 24902' 2017-01-17T08:23:42.176563Z 0 [Note] Plugin group_replication reported: 'client connected to db2 24902 fd 71' 2017-01-17T08:23:42.176876Z 0 [Note] Plugin group_replication reported: 'connecting to db1 24901' 2017-01-17T08:23:42.177312Z 0 [Note] Plugin group_replication reported: 'client connected to db1 24901 fd 73' 2017-01-17T08:23:43.463474Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_snapshot' 2017-01-17T08:23:43.463969Z 0 [Note] Plugin group_replication reported: 'new state x_recover' 2017-01-17T08:23:43.464000Z 0 [Note] Plugin group_replication reported: 'state 4277 action xa_complete' 2017-01-17T08:23:43.464275Z 0 [Note] Plugin group_replication reported: 'new state x_run' 2017-01-17T08:23:44.619112Z 0 [Note] Plugin group_replication reported: 'Starting group replication recovery with view_id 14844510167669342:17' --#（2） 开始进行组内数据recovery 2017-01-17T08:23:44.619451Z 34 [Note] Plugin group_replication reported: 'Establishing group recovery connection with a possible donor. Attempt 1/10' 2017-01-17T08:23:44.624181Z 34 [Note] 'CHANGE MASTER TO FOR CHANNEL 'group_replication_recovery' executed'. Previous state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. New state master_host='hch_test_web_1_24', master_port= 3317, master_log_file='', master_log_pos= 4, master_bind=''. 2017-01-17T08:23:44.628853Z 34 [Note] Plugin group_replication reported: 'Establishing connection to a group replication recovery donor 664b9ce9-d7de-11e6-9e8c-18a99b763071 at hch_test_web_1_24 port: 3317.' 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 'START SLAVE Syntax' in the MySQL Manual for more information. 2017-01-17T08:23:44.635870Z 36 [Note] Slave SQL thread for channel 'group_replication_recovery' initialized, starting replication in log 'FIRST' at position 0, relay log './bpe_service-relay-bin-group_replication_recovery.000001' position: 4 2017-01-17T08:23:44.681897Z 35 [Note] Slave I/O thread for channel 'group_replication_recovery': connected to master 'repl@hch_test_web_1_24:3317',replication started in log 'FIRST' at position 4 2017-01-17T08:43:34.219952Z 34 [Note] Plugin group_replication reported: 'Terminating existing group replication donor connection and purging the corresponding logs.' 2017-01-17T08:43:34.220609Z 36 [Note] Slave SQL thread for channel 'group_replication_recovery' exiting, replication stopped in log 'binlog.000042' at position 185511578 2017-01-17T08:43:34.226869Z 35 [Note] Slave I/O thread killed while reading event for channel 'group_replication_recovery' 2017-01-17T08:43:34.226886Z 35 [Note] Slave I/O thread exiting for channel 'group_replication_recovery', read up to log 'binlog.000042', position 185511578 2017-01-17T08:43:34.269973Z 34 [Note] '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=''. New state master_host='<NULL>', master_port= 0, master_log_file='', master_log_pos= 4, master_bind=''. -- # （3）已经数据恢复完成，加入组，成为组成员 2017-01-17T08:43:34.290920Z 0 [Note] Plugin group_replication reported: 'This server was declared online within the replication group'
概要: mysql グループレプリケーションの使用については、mongodb のシャーディングやプライマリセカンダリの考え方などの概念を参照すると理解しやすくなります。
以上がMySQL グループ レプリケーションの RECOVERING ステータスについての深い理解の詳細内容です。詳細については、PHP 中国語 Web サイトの他の関連記事を参照してください。
![[Web フロントエンド] Node.js クイック スタート](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
