Comments - Maxadmin

7 years, 4 months ago Yiannis Sot

I have a normal set up with 1 master and 1 slave. I stop the master in order to trigger a failover. In the database level I can see that the slave is now a master and that the previous master is down.

I tried to set the slave as master through maxadmin ( maxadmin set server2 master ) but after a while it turns back to slave/running again ( lost_master [Master, Running] -> [Running] ) and I cannot connect through Maxscale. Why is this happening?

 
7 years, 4 months ago Markus Mäkelä

The server loses the master status because the monitor overwrites the status on the next monitoring interval. To prevent this from happening, stop the monitor with maxadmin shutdown monitor <monitor name> and then set the server as master. You can start the monitor again with maxadmin restart monitor <monitor name>.

 
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.