1,初始主节点宕机
当mysql服务进程还在:
执行如下命名
mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | efce3b94-e7ba-11e8-b99c-005056237187 | ndb01 | 3306 | ERROR |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
发现集群状态已经为ERROR
停止同步服务进程执行
stop group_replication;
mysql> select * from performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+-------------
MGR 多主模式节点宕机重启
最新推荐文章于 2024-07-01 15:32:10 发布
本文详细介绍了MGR多主模式下,不同情况的节点宕机及重启过程。当主节点宕机,可通过停止并重新启动同步服务使节点恢复。若服务进程已死,重启mysql服务后,使用`start group_replication`恢复。在所有节点都宕机的情况下,需设置`group_replication_bootstrap_group`为ON,并从新主节点开始集群。
摘要由CSDN通过智能技术生成