Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the failure of MySQL 8.0 InnoDB Cluster

2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

The following brings you about MySQL 8.0 InnoDB Cluster failure how to solve the content, I believe you must have read a similar article. What's the difference between what we bring to everyone? Let's take a look at the text. I believe you will gain something after reading how to solve the failure of MySQL 8.0 InnoDB Cluster.

InnoDB Cluster one node is missing

Initialize the failed node

Systemctl stop mysqldrm-rf / var/lib/mysql/*systemctl start mysqld

Export the database of the normal node and transfer it to the failed node

Mysqldump-- all-databases-- triggers-- routines-- events-- quick-- single-transaction-- flush-logs-- master-data=2 > dbs.dumpscp dbs.dump 192.168.1.224

The failure node imports the database

Mysql > set sql_log_bin=0;mysql > ALTER USER root@'localhost' IDENTIFIED BY 'MySQL8.0';mysql > source dbs.dumpmysql > set sql_log_bin=1

Restart the failed node MySQL

Systemctl restart mysqld

Rejoin the failed node into the cluster

MySQL 192.168.1.226 MySQL 33060 + ssl JS > var cluster=dba.getCluster ('appCluster') MySQL 192.168.1.226 MySQL 33060 + ssl JS > cluster.removeInstance (' root@192.168.1.224:3306') MySQL 192.168.1.226 appCluster' 33060 + ssl JS > cluster.addInstance ('root@192.168.1.224:3306')

The cluster returns to normal.

MySQL 192.168.1.226 clusterName 33060 + ssl JS > cluster.status () {"clusterName": "appCluster", "defaultReplicaSet": {"name": "default", "primary": "192.168.1.226 Vera 3306", "ssl": "REQUIRED", "status": "OK", "statusText": "Cluster is ONLINE and can tolerate up to ONE failure." "topology": {"192.168.1.224 topology 3306": {"address": "192.168.1.224 mode", "readReplicas": {}, "role": "HA" "status": "ONLINE"}, "192.168.1.225 status 3306": {"address": "192.168.1.225 mode", "readReplicas": {}, "role": "HA" "status": "ONLINE"}, "192.168.1.226 mode 3306": {"address": "192.168.1.226 mode": "R HA W", "readReplicas": {}, "role": "HA" "status": "ONLINE"}}, "groupInformationSourceMember": "mysql://root@192.168.1.226:3306"

}

For the above about MySQL 8.0 InnoDB Cluster failure how to solve, do you think it is what you want? If you want to know more about it, you can continue to follow our industry information section.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report