下文给大家带来有关MySQL 8.0 InnoDB Cluster出现故障如何解决内容，相信大家一定看过类似的文章。我们给大家带来的有何不同呢？一起来看看正文部分吧，相信看完MySQL 8.0 InnoDB Cluster出现故障如何解决你一定会有所收获。
InnoDB Cluster 一节点丢失
初始化故障节点
systemctl stop mysqld rm -rf /var/lib/mysql/* systemctl start mysqld
导出正常节点的数据库，并传到故障节点
mysqldump --all-databases --triggers --routines --events --quick --single-transaction --flush-logs --master-data=2 > dbs.dump scp dbs.dump 192.168.1.224:~/
故障节点导入数据库
mysql> set sql_log_bin=0; mysql> ALTER USER root@'localhost' IDENTIFIED BY 'MySQL8.0'; mysql> source dbs.dump mysql> set sql_log_bin=1;
重启故障节点 MySQL
systemctl restart mysqld
将故障节点重新加入集群
MySQL 192.168.1.226:33060+ ssl JS > var cluster=dba.getCluster('appCluster')
MySQL 192.168.1.226:33060+ ssl JS > cluster.removeInstance('root@192.168.1.224:3306')
MySQL 192.168.1.226:33060+ ssl JS > cluster.addInstance('root@192.168.1.224:3306')集群恢复正常
MySQL 192.168.1.226:33060+ ssl JS > cluster.status()
{
"clusterName": "appCluster",
"defaultReplicaSet": {
"name": "default",
"primary": "192.168.1.226:3306",
"ssl": "REQUIRED",
"status": "OK",
"statusText": "Cluster is ONLINE and can tolerate up to ONE failure.",
"topology": {
"192.168.1.224:3306": {
"address": "192.168.1.224:3306",
"mode": "R/O",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
},
"192.168.1.225:3306": {
"address": "192.168.1.225:3306",
"mode": "R/O",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
},
"192.168.1.226:3306": {
"address": "192.168.1.226:3306",
"mode": "R/W",
"readReplicas": {},
"role": "HA",
"status": "ONLINE"
}
}
},
"groupInformationSourceMember": "mysql://root@192.168.1.226:3306"}
对于上文关于MySQL 8.0 InnoDB Cluster出现故障如何解决，大家觉得是自己想要的吗？如果想要了解更多相关，可以继续关注我们的行业资讯板块。
免责声明：本站发布的内容（图片、视频和文字）以原创、转载和分享为主，文章观点不代表本网站立场，如果涉及侵权请联系站长邮箱：is@yisu.com进行举报，并提供相关证据，一经查实，将立刻删除涉嫌侵权内容。
