In the replication FAQ regarding redundancy/high availability. Its example looks as if it could be ... wrong.
: http://dev.mysql.com/doc/mysql/en/Replication_FAQ.html


The basic method is to use one of the slaves as the master in the case where the master goes down. The potential problem that I see is that if S1 is behind S2 in the binlog then wouldn't S2 become confused when you tell it to replicate of S1 ... because S1 would never be able to catch up to S2.

Is there a way to tell the Master to guarantee updates to the slaves go in a particular order?

In the diagrams below M (the master) fails and we start to treat S1 as the master.

       WC
        \
         v
 WC----> M
       / | \
      /  |  \
     v   v   v
    S1   S2  S3


WC / | WC | M(unavailable) \ | \ | v v S1<--S2 S3 ^ | +-------+


.. yes this could have gone in the doc mailing list, but I figured I would get a better answer here.


Mike


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to