您的位置:首页 > 数据库 > MySQL

MySQL 8.0 InnoDB Cluster 恢复故障成员

2018-09-20 10:31 1406 查看

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 恢复 故障成员