List:General Discussion« Previous MessageNext Message »
From:Mike Diehl Date:June 13 2011 9:28pm
Subject:Re: Mysql Failover Recommendations
View as plain text  
I received a recommendation to look at MySQL-MMM

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 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 

That said, Mysql Proxy and HA Proxy seem to be the front-runners.

Any additional comments are certainly welcome.


On Monday 13 June 2011 3:16:26 pm Johan De Meersman wrote:
> ----- Original Message -----
> > From: "Mike Diehl" <mdiehl@stripped>
> > 
> > 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
> I've seen many people rave, but my experience is close to yours: if you
> want something, figure it out yourself.
> > Ha Proxy
> 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
> Unknown to me.
> People also rave about MMM, haven't much looked at it, yet.


Take care and have fun,
Mike Diehl.
Mysql Failover RecommendationsMike Diehl13 Jun
  • Re: Mysql Failover RecommendationsJohan De Meersman13 Jun
    • Re: Mysql Failover RecommendationsMike Diehl13 Jun
    • Re: Mysql Failover RecommendationsAndrew Moore13 Jun