MySQL Router should be a load balancer and high availability manager for MySQL. It is, to some extent. What bothers me is its low resilience and limited capacity to handle substantial numbers of connections.
MySQL Router is the orphaned offspring of the failed and terrible project: MySQL Proxy. A badly put together and poor design, erratic and senseless, which even ran scripts in LUA. It never had support and was full of bugs. So much so that it was never classified beyond “Alpha Release.” With a quick facelift, it became MySQL Router.
It remains as unstable as ever. But its eternal connection limit is indecent. Who needs to load balance a database server with few connections?
Since 2016, that is for 2 years now, there is bug 80260 that accounts for the 500 connections limit. Recently, I reported bug 90739. But due to the response, I concluded that there will be no fix.
If the guy’s limit is 500 connections, and you have 2 servers, each will get 250 connections. What? A 500 total connections limit for a cluster only makes sense if the queries are VERY POORLY WRITTEN! Otherwise, it’s nonsense.
Therefore, my recommendation remains not to use MySQL Proxy 0.8 Alpha, oops, I mean MySQL Router 2.1.5.
Visit our Blog
Learn more about databases
Learn about monitoring with advanced tools
Have questions about our services? Visit our FAQ
Want to see how we’ve helped other companies? Check out what our clients say in these testimonials!
Discover the History of HTI Tecnologia
