MySQL Forums :: Utilities :: Load Balancing vs MySQL Fabric


Advanced Search

Re: Load Balancing vs MySQL Fabric
Posted by: Rick James ()
Date: March 05, 2016 12:28AM

"Caching a connection" is at odds with "reconnecting after a server goes away".

In Fabric's case, the Fabric connector + Fabric node will (as I understand it) find the new place to connect to. Unfortunately, the Fabric node becomes the single-point-of-failure. So the question becomes one of hardening the Fabric node vs hardening the Master.

Even simple DNS A-records (and AAAA-records) is an approach to load balancing. It suffers from the tradeoff between short TTL versus pounding on the DNS server. But it has the SPOF pretty much solved -- you have a short list of hard-coded IP addresses of DNS servers.

Options: ReplyQuote


Subject Views Written By Posted
Load Balancing vs MySQL Fabric 1612 Jerry Richart 02/17/2016 04:43PM
Re: Load Balancing vs MySQL Fabric 582 Rick James 02/20/2016 03:40PM
Re: Load Balancing vs MySQL Fabric 582 james wang 02/22/2016 03:18AM
Re: Load Balancing vs MySQL Fabric 565 Jerry Richart 02/22/2016 10:42AM
Re: Load Balancing vs MySQL Fabric 569 Jerry Richart 02/22/2016 11:14AM
Re: Load Balancing vs MySQL Fabric 595 Rick James 02/22/2016 06:23PM
Re: Load Balancing vs MySQL Fabric 569 Jerry Richart 02/29/2016 10:55AM
Re: Load Balancing vs MySQL Fabric 534 Rick James 03/05/2016 12:28AM
Re: Load Balancing vs MySQL Fabric 506 Nick Swenson 03/18/2016 03:31PM
Re: Load Balancing vs MySQL Fabric 674 OUERDIA BOUDJEDAIMI 03/28/2016 03:12PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.