Recently we have been investigating running Percona cluster with ProxySQL on Docker Swarm, the following guide for reference: Scaling Percona XtraDB Cluster with ProxySQL in Docker Swarm - Percona Database Performance Blog
Since ProxySQL is SQL load balancer in this Docker Stack, how could I set it up so that we could have active/passive ProxySQL containers running on two runners node with nearly instant fail-over, so all application will still using the same DB hostname / IP as target without changing anything?
(And please, I don’t make the rule nor bends it, that’s our business requirement to have IP HA available on Docker Swarm)
Hi,
With ProxySQL the first question you need to answer is: Where do i put it? You can check this blog post https://www.percona.com/blog/2017/07/20/where-do-i-put-proxysql/ but pretty much is either in the same server (or container) used by your apps or on its own layer. The suggested approach is always app+proxysql together and use the ProxySQL Cluster solution ( https://proxysql.com/documentation/ProxySQL-Cluster/ ) to keep configuration in sync.
And for HA you could use Keepalived to move the Virtual IPs, as described here: https://www.percona.com/blog/2017/01/19/setup-proxysql-for-high-availability-not-single-point-failure/ However, implementation within Swarm might be different