Re: Use Case: Distribute INSERTS/UPDATES to several masters

[Patrick Feliciano]

another option would be to use master-master replication for your 2 write machines with mysql-proxy doing regular load splitting between the 2. This way you have NO downtime on individual server failure. Mysql-proxy will just continue to send writes to the currently up server and when the down server comes back online set its access port to something besides the default to mysql-proxy doesn't send traffic to it while it catches up replication then when it does restart with the default port again and you are back to full capacity.

This config lets you have 0 downtime, more write throughput and no "dark" hardware sitting on your rack waiting to failover.

The only other point to consider would be failover for replication from slave servers... since if the master that the slaves were replicating from went down they would become out of sync, though that could probably be overcome by using multi-master replication. That is something I'd have to research.