Release 2.4.13 is a GA release.
Released: 19 Oct 2020
This document describes the changes in release 2.4.13, when compared to the previous release in the same series.
For any problems you encounter, please consider submitting a bug report on our Jira.
Now packages are signed by MariaDB Enterprise key. Public key is here MariaDB-Enterprise-GPG-KEY
MaxScale crashes in gwbuf_set_type() upon query retry
Abort due to double free or corruption after "Write to Client DCB ... state DCB_STATE_POLLING failed"
MariadbMon documentation needs to take 10.5 privilege changes into account
Fix download link in documentation
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 .
MXS-3165 cache_inside_transactions vs cache_in_transactions
MXS-3149 Monitor should remove [Master] when starting swithover
MXS-3143 FOUND_ROWS() not routed to previous target
MXS-3132 Monitor timeout defaults are wrong
MXS-3131 Monitor module not displayed in show monitors
MXS-3123 Documentation: KB page for 2.4 does not mention maxctrl way to rotate the log
MXS-2680 Monitor type not shown in show monitors