Release 2.4.8 is a GA release.
Released: 18 Mar 2020
This document describes the changes in release 2.4.8, when compared to the previous release in the same series.
For any problems you encounter, please consider submitting a bug report on our Jira.
Memory leak in alter maxscale
max_slave_replication_lag uses servers with unknown replication lag
qc_sqlite leaks memory with complex CREATE TABLE query
Logrotate warnings when PID file does not exist
warning: The query can't be routed to all backend servers because it includes SELECT and SQL variable modifications which is not supported.
UnhandledPromiseRejectionWarning when creating a new filter
Monitor connections do not insist on SSL being used
Router diagnostic output is not documented
maxctrl fails to destroy binlogrouter service
Cannot configure Connector-C TLS version
Using DIV function in query produces an error
TLS/SSL setup is not a part of the server mini-tutorial
optimize table: Query could not be tokenized/Parsing the query failed, cannot report query type
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded .
The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.
The source code is available .