Skip to content
dbdeployer

Quick Start: ProxySQL Integration

dbdeployer can deploy a ProxySQL instance alongside a replication topology, pre-configured with read/write splitting. Assumes MySQL 8.4 is already unpacked (see Quick Start: MySQL Single).

Prerequisites

Section titled “Prerequisites”
  • dbdeployer installed with MySQL 8.4 unpacked in ~/opt/mysql/
  • ProxySQL binary available on PATH (e.g. /usr/bin/proxysql)

1. Deploy replication with ProxySQL

Section titled “1. Deploy replication with ProxySQL”
Terminal window
dbdeployer deploy replication 8.4.4 --with-proxysql

Expected output:

Replication directory installed in $HOME/sandboxes/rsandbox_8_4_4
master on port 20192
slave1 on port 20193
slave2 on port 20194
ProxySQL admin on port 6032
ProxySQL proxy on port 6033

dbdeployer starts the MySQL topology, launches ProxySQL, and configures hostgroups for write (master) and read (slaves).

2. Open the ProxySQL admin interface

Section titled “2. Open the ProxySQL admin interface”
Terminal window
~/sandboxes/rsandbox_8_4_4/proxysql/use

You are now in the ProxySQL admin shell. Inspect the hostgroups:

SELECT hostgroup_id, hostname, port, status FROM runtime_mysql_servers;

3. Connect through the proxy

Section titled “3. Connect through the proxy”
Terminal window
~/sandboxes/rsandbox_8_4_4/proxysql/use_proxy

This opens a MySQL connection routed through ProxySQL on port 6033. Writes are sent to the master; reads are distributed across the slaves automatically.

Try it:

-- this SELECT will be routed to a slave
SELECT @@hostname;


-- DML is routed to the master
CREATE DATABASE proxydemo;

4. Clean up

Section titled “4. Clean up”
Terminal window
dbdeployer delete rsandbox_8_4_4

This stops ProxySQL and all MySQL nodes and removes the sandbox directory.

What’s next?

Section titled “What’s next?”