Skip to content
Percona Software for MySQL Documentation

For help, click the link below to get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona build of ProxySQL, proxysql-admin, and percona-scheduler-handler documentation

This documentation is for the latest release: Percona ProxySQL admin tools 2.7.3 (Release notes).

Percona distributes ProxySQL from the upstream project without code changes and provides additional tools like proxysql-admin for easier integration with Percona XtraDB Cluster. ProxySQL is a high-performance proxy that sits between client applications and Percona XtraDB Cluster. The proxy manages a connection pool by caching database connections and keeping those connections open for future use. This behavior reduces the overhead of repeatedly establishing and tearing down connections for each SQL request.

Without a connection pool, every SQL query would require a new connection to a cluster node, which would be closed after the query completed. ProxySQL maintains selected connections and reuses them as needed or closes unused connections after a defined idle time. Client applications connect to ProxySQL, which forwards database traffic to the XtraDB Cluster.

The ProxySQL service runs as a daemon and is monitored by a watchdog process capable of restarting it in case of unexpected termination, which helps minimize downtime. The daemon receives traffic from MySQL clients and forwards it to backend MySQL-compatible servers.

Configuration is handled using SQL-like statements, including runtime options, server grouping, and query routing rules. Most settings can be changed dynamically without restarting the proxy.

The ProxySQL 2 documentation includes detailed guidance on installation, operation, and the use of supporting tools. The maintained releases are listed on ProxySQL Installation.

You can download Percona’s build of ProxySQL 2.x.x. Note that Version 1 is no longer actively maintained. The ProxySQL 2. x. x downloads may include:

In a MySQL 8.4 or Percona Server for MySQL 8.4 environment, you may face these issues:

  • ProxySQL contains counters that have not been updated to use the new terminology, leading to unexpected results.

  • The binlog reader errors out during initialization due to the use of old terminology, such as the SHOW MASTER STATUS command

Last update: 2025-06-02