MySQL failover with orchestrator and ProxySQL
summary
Shows a concrete build: a MySQL fleet using asynchronous replication, orchestrator hook updates ProxySQL to change routing automatically, and scripted failover exercised end to end so the routing and replication roles actually switch. Describes patch workflow of updating a replica then failing over, claims no manual intervention, and surfaces operational details and pitfalls for achieving fast automated failover and keeping clients routed correctly without prolonged outages.
AI-written summary · about
related talks
55mProduction with ProxySQL and Orchestrator
08mMySQL as a Layered Service: How to use Proxy SQL to Control Traffic and Scale Out
41mAutopsy of a MySQL Automation Disaster
55mProxySQL Use Case Scenarios
50m#ProxySQL Use Case Scenarios
46mDatabase Reliability Engineering for MySQL
37mScale MySQL beyond limits with ProxySQL
35mMySQL HA, Recovery and Load Balancing
