Release 2.5.17 is a GA release.
Released: 13 Dec 2021
This document describes the changes in release 2.5.17, when compared to the previous release in the same series.
If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.
For any problems you encounter, please consider submitting a bug report on our Jira.
MaxScale unconditionally loads global options from /etc/maxscale.cnf.d/maxscale.cnf
test_kafkacdc fails in 2.5
Kerberos tests are skipped in 2.5
The pam_authentication_2fa test fails very often
core dumps from system-tests (meta bug)
Pinloki initial gtid scan incorrectly reads entire files
Errors with causal_reads and read-only transactions
Sending binlog events is inefficient
Document privileges required for procs_priv system table
Allow maintenance mode to be set on Galera cluster master
Allow symbolic link for path to directory /usr/share/maxscale/gui
The location of the GUI web directory isn't documented
Queries are not always counted as reads with router_options=slave
maxscale crash
maxscale rpl_state is empty
SQL_MODE parsing sometimes fails
When MariaDBMonitor acquires lock majority, the log message gives the impression that auto_failover is enabled even when it is not configured
Unexpected internal state with read-only cursor and result with one row
Not enough information in server state change messages
session_track_trx_state set to true causes incorrect routing of SELECT
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 .