Re: slave to master
- Date: Fri, 29 Apr 2016 14:49:57 -0400
- From: william drescher <william@xxxxxxxxxxxxxxx>
- Subject: Re: slave to master
On 4/28/2016 5:20 PM, Thomas wrote:
At some point you will want to stop the slave so that it will not
start replicating when the master comes back up.
I have setup an master slave replication.
This works fine.
I have running an Apache webserver and some other programms accessing the
Whats the standard pocedure if master fail?
I want to start up the programms on the slave by hand and then they are
accessing the mySQL slave. Can they write to the slave or do I have to change
something before in the mysql slave configuration?
The simple answer is that you don't have to do anything.
When the master is repaired and up you need to stop the programs
on the slave from accessing mysql (ie: stop the programs on the
slave), make a database copy of the slave, copy it to the master
and reload the database on the master, and then use the Change
Master to command on the slave to set up the slave to begin
replicating and start slave.
This is the poor man's failover for low volume systems.
In essence the slave becomes the main database server until you
are ready to restart the master and replication.
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql