Yakir Gibraltar
05/18/2026, 6:17 AMMichael Taranov
05/18/2026, 8:37 AMRocky
05/18/2026, 8:38 AMMichael Taranov
05/18/2026, 8:38 AMRocky
05/18/2026, 8:38 AMGroup 1 for Cluster A, Group 2 for Cluster B).
* Runtime Updates: To perform a switchover, you simply update the mysql_servers table to point your production traffic (the Hostgroup used by your apps) to the new cluster's IP addresses and execute LOAD MYSQL SERVERS TO RUNTIME. This redirects traffic instantly without requiring application restarts.
* Query Routing: You can use mysql_query_rules to mirror traffic or route specific users/queries to the standby cluster for testing before a full cutover.
2. Reducing Connection Counts
* Multiplexing: ProxySQL maintains a pool of persistent connections to the StarRocks FEs. It can map thousands of frontend application connections to a much smaller number of backend connections, significantly reducing the overhead on the FE nodes.
Other Recommended Tools
While ProxySQL is the most "intelligent" for SQL routing, other standard tools are also commonly used with StarRocks:
* HAProxy / Nginx: Often used for simple TCP-level load balancing. They are lightweight but lack SQL-aware features like read/write separation or query-level routing.
* Keepalived: Frequently used alongside HAProxy or ProxySQL to provide a Virtual IP (VIP) for high availability of the proxy layer itself.
* JDBC Load Balancing: If your application uses Java, the MySQL JDBC driver supports jdbc:mysql:<loadbalance://host1>,host2/db, which provides basic client-side failover and load balancing without an external proxy.
Data Synchronization for Switchover
For a truly "smooth" switchover, your data must be in sync. StarRocks provides Cross-cluster Replication (CCR), which allows you to replicate data from a source cluster to a target cluster at the database or table level to ensure the standby cluster is ready for traffic.
References
• administration/data_migration_tool.md
• administration/stargo.md
• administration/Meta_recovery.md