Is Mysql Switchover / Failover mechanisam supported prior to version 4.1?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • amit2781
    New Member
    • Jun 2009
    • 23

    Is Mysql Switchover / Failover mechanisam supported prior to version 4.1?

    Hi,

    Does "Switching Masters During Failover" supports for prior to version 4.1?

    I found this point in 5.0 onward manual and not in "MySQL 3.23/4.0/4.1" manual.

    Can you please tell me it is supported in prior to 4.1 versions?

    Regards,
    Amit
  • Atli
    Recognized Expert Expert
    • Nov 2006
    • 5062

    #2
    Hey.

    The first sentence from 16.2.6. Switching Masters During Failover
    There is currently no official solution for providing failover between master and slaves in the event of a failure.
    No version of MySQL supports this mechanism. The manual for the 5.x version just provides a guide so that you can replicate the behavior in your code.

    Having never actually attempted this, I would assume the same theory can be applied to the versions 4 and 3, although some modifications may be required to bridge the version cap.

    Comment

    • amit2781
      New Member
      • Jun 2009
      • 23

      #3
      Hi Atli,

      Thanks for the prompt reply.

      It is ok that there is no any official solution.

      I have made the same setup using the details given in :
      How To Set Up Database Replication In MySQL This tutorial describes how to set up database replication in MySQL. MySQL replication allows you to h...


      Consider x.x.x.x - Slave , y.y.y.y - Master

      My case is now my master(y.y.y.y. ) goes down and Slave(x.x.x.x) need to become a master.

      I am doing the steps given in guide as:
      "On the slave Slave 1 being promoted to become the master, issue STOP SLAVE and RESET MASTER."

      I have fired a same command on my "x.x.x.x."

      Again when Master gets up it should become a slave(y.y.y.y) of x.x.x.x (which is now master)

      As in guide they said that ->

      When Master is up again, you must issue on it the same CHANGE MASTER TO as that issued on Slave 2 and Slave 3, so that Master becomes a slave of S1 and picks up each Web Client writes that it missed while it was down.


      I just tried the same thing manually but it is not working only applying "CHANGE MASTER TO " on master to become a slave(y.y.y.y) of master(x.x.x.x) .

      Is there any remaining task to be done to have successful setup like this?

      Any help on this highly appreciated.

      Amit

      Comment

      Working...