The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-16. For the latest, interactive version please visit https://mariadb.com/kb/.

Galera Cluster - Adding node after crash

I'm working on a project in which I have a cluster of 3 nodes. On each one of these node, I have a service that need Mariadb to start and work correctly. The replication and the cluster work correctly but I actually working on crash recovery. If a power failure, or a crash occure on a node, Mariadb will stop working to avoid split brain situation. But, as said before, I need Mariadb to make my service work. Once this node is disconnected from the cluster, I ever tried to set to "Primary" with the command SET GLOBAL wsrep_provider_options='pc.bootstrap=YES'; My problem is that I can't get this node back the cluster without completly restarting nodes and without getting some errors. I ever worked with Galera Arbitrator, but it didn't solve my problem. Have someone an idea to add a node with a "Primary" status in a existing cluster ? Thanks for your answers.

Answer Answered by Daniel Black in this comment.

Does this galera documentation - https://galeracluster.com/library/training/tutorials/restarting-cluster.html help (looks to be 2014 at the moment).

There is also the galera-new-cluster - https://galeracluster.com/library/documentation/crash-recovery.html recommends this.

Galera Arbitrator has very limited use, so I'd stick to a few actual nodes rather than this testing utility (that has a limited production use on more than 3 nodes sometimes).

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.