Issues with MySQL Replication?

Because it is simple to setup, MySQL Replication is probably the most widely used mechanism to provide high availability. Unfortunately, it is also somewhat fragile:

-       Fail-over is not automatic and has to be performed by somebody who is very skilled

-       Slaves can easily end up with different data to the master, due to hardware problems, software bugs or the use of non-deterministic functions. Diverging datasets on master and slave servers causes replication to stop.

-       A crashing master can cause corruption of the binary log. When it is restarted, the slave servers would not be able to continue from the last binary log position.

It is also possible to set up two-way replication between two mysql servers. However, ring topologies are not recommended. MySQL Replication currently does not support any locking protocol between master and slave to guarantee the atomicity of a distributed updated across two different servers.