我有一个三节点的 galera 集群。其中一个节点（它是一个被动节点，不是主动使用的节点）死亡，并且 mysql 无法在此主机上重新启动：
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-07-21T14:55:39Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
2023-07-21T14:55:39.744960Z 0 [ERROR] [MY-012684] [InnoDB] [FATAL] is_short 0, info_and_status_bits 0, offset 9008, o_offset 6, mismatch index 18446744073709551613, end_seg_len 17 parsed len 3
BuildID[sha1]=d25f43b20ff93c5ab45e72e5201c79269b541a30
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
2023-07-21T14:55:39.745031Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: page0cur.cc:1177:ib::fatal triggered thread 139622639150848
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
我不想摆弄恢复 innodb 等 - 我猜最简单的方法是删除这个节点并将其重新加入到集群。
所以我的问题是如何“清理”故障主机上的 mySQL，以便从其他两个剩余节点获得完全同步？
谢谢帕特里克
答案1
解决了：
1.) 在 mysql 配置中使用“wsrep”禁用所有内容 2.) 重新初始化 mysql (mysqld --initialize) 3.) 再次启用“wsrep”配置 4.) 重新启动 mysql = 同步现在正在运行，状态再次变为主要