MariaDB MaxScale 2.1.2 Release Notes -- 2017-04-03

MariaDB MaxScale 2.1.2 Release Notes -- 2017-04-03

Release 2.1.2 is a Beta release.

This document describes the changes in release 2.1.2, when compared to release 2.1.1.

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

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

Changed Features

Formatting of IP Addresses and Ports

All messaging that contains both the address and the port are now printed in an IPv6 compatible format. The output uses the format defined in RFC 3986 and STD 66.

In practice this means that the address is enclosed by brackets. The port is separated from the address by a colon. Here is an example of the new format:


The first is an IPv4 address, the second an IPv6 address and the last one is a hostname. All of the addresses use port 3306.


  • The storage storage_inmemory is now the default, so the parameter storage no longer need to be set explicitly.

Improved Wildcard Matching

The MySQLAuth module now supports all types of wildcards for both IP addresses as well as hostnames.

Configurable Connector-C Plugin Directory

The Connector-C used by MaxScale can now be configured to load authentication plugins from a specific directory with the new connector_plugindir parameter. Read the Configuration Guide for more details about this new parameter.

New Features

IPv6 Support

MaxScale now supports IPv6 connections on both the client and backend side as well as being able to listen on IPv6 addresses.

Bug fixes

Here is a list of bugs fixed since the release of MaxScale 2.1.1.

  • MXS-1032 missing plugin

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.


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 X.Y.Z. Further, master always refers to the latest released non-beta version.

The source code is available here.


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.