On Tue, Oct 19, 2010 at 19:06, John Daisley wrote:
> You may also want to take a look at MySQL MMM which makes use of
> Active/passive masters to makes MySQL failover very simple.
+1 We could not do much of our daily work without MMM. It makes
the whole HA/Failover thing a breeze. We have it i
The short answer is this: You need special software outside of MySQL to do
this. This software has to
- Keep a heartbeat going between the two servers. Whether or not you do this
by checking only MySQL, or the machines themselves, depends upon what other
applications might be running (web serve
You may also want to take a look at MySQL MMM which makes use of
Active/passive masters to makes MySQL failover very simple.
On 19 October 2010 11:45, Johan De Meersman wrote:
> That's pretty much it, indeed. You need to make absolutely sure that no
> more
> connections can be made to the old,
That's pretty much it, indeed. You need to make absolutely sure that no more
connections can be made to the old, broken master, though - even if you have
to physically pull the network or power cable. Failover services refer to
this as STONITH: Shoot The Other Node In The Head.
Don't think "but it
Quoting Machiel Richards :
The question I have however is how do you fail over to the slave
server in the event that the master server is unavailable and then how
to revert back to the master server once the server is available again.
Hi,
to fail over to the slave, you dont need t
