MariaDB MaxScale 2.1.10 Release Notes

Release 2.1.10 is a GA release.

This document describes the changes in release 2.1.10, when compared to release 2.1.9.

If you are upgrading from release 2.0, please also read the following release notes:

• 2.1.9
• 2.1.8
• 2.1.7
• 2.1.6
• 2.1.5
• 2.1.4
• 2.1.3
• 2.1.2
• 2.1.1
• 2.1.0

For any problems you encounter, please consider submitting a bug report at Jira.

Changed Features

Internal Query Retries

The internal SQL queries that MaxScale executes to load database users as well as monitor the database itself can now be automatically retried if they are interrupted. The new global parameter, query_retries controls the number of retry attempts each query will receive if it fails due to a network problem. The query_retry_timeout global parameter controls the total timeout for the retries.

To enable this functionality, add query_retries=<number-of-retries> under the [maxscale] section where <number-of-retries> is a positive integer.

Bug fixes

Here is a list of bugs fixed in MaxScale 2.1.10.

• MXS-1456 OOM when script variable is empty
• MXS-1451 Password is not stored with skip_authentication=true
• MXS-1450 Maxadmin commands with a leading space are silently ignored
• MXS-1449 Database change not allowed

Packaging

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

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.

The source code is available here.