I received a recommendation to look at MySQL-MMM http://mysql-mmm.org/.
However, my two servers are in different parts of the country, so I can't use any IP-based fail over solution. I truly need a proxy that listens on 127.0.0.1 and forwards to either the "local" server, of if needed, to another "remote" server. My system isn't under heavy load, but it simply can not be down... if at all possible. That said, Mysql Proxy and HA Proxy seem to be the front-runners. Any additional comments are certainly welcome. Mike. On Monday 13 June 2011 3:16:26 pm Johan De Meersman wrote: > ----- Original Message ----- > > > From: "Mike Diehl" <mdi...@diehlnet.com> > > > > I'm about to set master-master replication and would like to get > > recommendations as to the best method for getting my applications to > > failover when needed. > > I should already be in bed, but as a very brief reply: I find automatic > failover of MySQL servers to be a thoroughly bad idea. Stick to manual > failover, regardless of what mechanism you implement. If you absolutely > must go automatic, be damn sure the supposedly failed node is dead and > buried before switching - kill it yourself if you have to (think > IP-enabled power switches). > > > MySQL Proxy http://forge.mysql.com/wiki/MySQL_Proxy > > I've seen many people rave, but my experience is close to yours: if you > want something, figure it out yourself. > > > Ha Proxy http://haproxy.1wt.eu/#fiab > > Works very well as a general solution, but may be a bit of overkill. Have a > look at Ultramonkey for good documentation and setups. > > > Pen http://siag.nu/pen/ > > Unknown to me. > > People also rave about MMM, haven't much looked at it, yet. -- Take care and have fun, Mike Diehl. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
