ProxySQL 1.4.12, released by ProxySQL, is now available for download in the Percona Repository along with an updated version of Percona’s proxysql-admin tool.
ProxySQL is a high-performance proxy, currently for MySQL and its forks (like Percona Server for MySQL and MariaDB). It acts as an intermediary for client requests seeking resources from the database. René Cannaò created ProxySQL for DBAs as a means of solving complex replication topology issues.
The ProxySQL 1.4.12 source and binary packages available at https://percona.com/downloads/proxysql include ProxySQL Admin – a tool, developed by Percona to configure Percona XtraDB Cluster nodes into ProxySQL. Docker images for release 1.4.12 are available as well: https://hub.docker.com/r/percona/proxysql/. You can download the original ProxySQL from https://github.com/sysown/proxysql/releases. GitHub hosts the documentation in the wiki format.
Improvements
- #68: Scripts are now compatible with Percona XtraDB Cluster (PXC) hosts using IPv6
- #107: In
include-slaves
, a slave would always be moved into the write hostgroup even if the whole cluster went down. A new option--use-slave-as-writer
specifies whether or not the slave is added to the write hostgroup.
Bugs Fixed
- #110: In some cases, pattern cluster hostname did not work with
proxysql-admin
. - #104:
proxysql-admin
testsuite bug fixes. - #113:
proxysql_galera_checker
assumed that parameters were given in the long format - #114: In some cases, ProxySQL could not be started
- #115:
proxysql_node_monitor
could fail with more than one command in the scheduler - #116: In some cases, the scheduler was reloading servers on every run
- #117: The
--syncusers
option did not work when enabling cluster - #125: The function
check_is_galera_checker_running
was not preventing multiple instances of the script from running
ProxySQL is available under Open Source license GPLv3.
Hello, I am experiencing the same problem which is fixed in 1.4.12: #117: The –syncusers option did not work when enabling cluster but in version proxysql2-2.0.7-1.2. Can you please confirm if this should be solved in 2.0.7 too and if there is such a problem and a way to avoid it?
Thank you in advance!