List:General Discussion« Previous MessageNext Message »
From:Jerry Schwartz Date:October 19 2010 2:09pm
Subject:RE: Failover on master/slave replication
View as plain text  
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 server, etc.)
- In the event of a failure, it should cause a shutdown of the primary server 
MACHINE.
- The secondary MACHINE should adopt the IP address of the failed primary.

Switching the machines back to the original configuration is done (or at least 
initiated) by hand, because you need to identify and fix whatever the problem 
was.

Regards,

Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032

860.674.8796 / FAX: 860.674.8341
E-mail: jerry@stripped
Web site: www.the-infoshop.com


>-----Original Message-----
>From: Machiel Richards [mailto:machielr@stripped]
>Sent: Tuesday, October 19, 2010 5:15 AM
>To: mysql mailing list
>Subject: Failover on master/slave replication
>
>Good day all
>
>        I am hoping someone has had some experience in this to assist
>me.
>
>        I have been going through lots of forums and documentation and
>can find a lot of information on how to setup a master/slave replication
>on MySQL.
>
>        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.
>
>        This is one thing I can't seem to get much info on unless I am
>looking in the wrong places.
>
>
>       I would really appreciate help on this one.
>
>
>Regards
>Machiel



Thread
Failover on master/slave replicationMachiel Richards19 Oct
  • Re: Failover on master/slave replicationa.smith19 Oct
    • Re: Failover on master/slave replicationJohan De Meersman19 Oct
      • Re: Failover on master/slave replicationJohn Daisley19 Oct
        • Re: Failover on master/slave replicationWalter Heck20 Oct
  • RE: Failover on master/slave replicationJerry Schwartz19 Oct