MariaDB MaxScale 21.06.20 Release Notes

Release 21.06.20 is a GA release.

This document describes the changes in release 21.06.20, 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.

Bug fixes

• MXS-5618 Maxctrl interactive mode doesn't use --tls-verify-server-cert=false
• MXS-5608 optimistic_trx causes a query to hang
• MXS-5599 Processing of conditional headers is incorrect
• MXS-5598 MaxCtrl fails to read large inputs from stdin
• MXS-5590 REST-API always sends a Connection: close header
• MXS-5582 Add a Service with a CLUSTER as its target breaks CONFIG SYNC
• MXS-5577 Aborted connection on backend mariadb with persistpool maxscale
• MXS-5576 Maxctrl config permission check error message is misleading
• MXS-5567 Wrong password in interactive mode is only seen after the first command
• MXS-5566 --secretsdir has no default value
• MXS-5563 Using PKCS#1 private key in the REST-API results in cryptic errors
• MXS-5556 Trailing parts of large session command are not routed correctly
• MXS-5542 kafkacdc commits offsets when it probes GTIDs from Kafka
• MXS-5541 Logs Archive page doesn't show useful API error
• MXS-5525 Masking with functions uses wrong rule settings

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

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 here.