Bypass MySQL "Too Many Connections" with Admin Port and MySQL 8.0.14 Features

Background

MySQL error 1040 (08004) “Too many connections” occurs when the server reaches the max_connections limit. This can be caused by mis‑configuration, oversized connection pools, or sudden load spikes, and prevents new client sessions from being established.

Percona Server solution (extra port)

Percona Server provides a dedicated administrator port that is not subject to the max_connections limit. By configuring an extra port with a single allowed connection, a DBA can still issue administrative commands when the main port is saturated.

Edit the MySQL configuration file (typically /etc/my.cnf) and add the following lines under the [mysqld] section:

extra_port = 3307
extra_max_connections = 1

Restart the MySQL service to apply the changes:

sudo service mysql restart

sudo systemctl restart mysql

Connect to the reserved admin port:

mysql -u<username> -p<password> -P3307 -h127.0.0.1

MySQL 8.0.14+ built‑in admin connection

Starting with MySQL 8.0.14, a native admin interface is available. Create a user with the SERVICE_CONNECTION_ADMIN privilege and enable the interface by setting two system variables: admin_address – IP address on which the admin port listens (e.g., 127.0.0.1 for local access). admin_port – default 33062; can be changed as needed.

Both variables require a server restart. The admin port has no connection limit, so DBA sessions remain possible even when max_connections is exhausted.

Experiment

An experiment with 300 concurrent normal client connections demonstrates the difference. The regular port quickly reaches the “Too many connections” error, while the admin port stays reachable.

Recommendations

For MySQL 8.0.14 or newer, enable the built‑in admin interface and grant SERVICE_CONNECTION_ADMIN only to DBA accounts. For older Percona Server installations, use the extra_port and extra_max_connections settings to retain a reserved admin connection.