The Ultimate Guide to High Availability with MariaDB

Comments - Changing a Replica to Become the Primary

3 years, 2 months ago Laurent Indermühle
Re: Changing a Slave to Become the Master

Is `FLUSH TABLES WITH READ LOCK;` the best way to lock the primary from receiving new queries? I had replications fails to restart after switchover many times. Then, I started using Orchestrator and never had an issue again. Turns out, Orchestrator [1] only set `SET GLOBAL read_only = ON;` on the primary before switchover. Then I read this answer https://dba.stackexchange.com/questions/74670/revoke-write-privileges-vs-setting-database-to-readonly which explain the advantages of read_only over FTWRL.

Other thing, in last chapter, "Now you can upgrade the new master to a newer version" should be "Now you can upgrade the OLD master to a newer version"

Thanks for your great documentation, Laurent Indermühle

[1] https://github.com/openark/orchestrator/blob/master/docs/topology-recovery.md#graceful-master-promotion

 
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.