Files
MaxScale/Documentation/Release-Notes/MaxScale-2.3.1-Release-Notes.md
2018-11-06 09:49:25 +02:00

2.4 KiB

MariaDB MaxScale 2.3.1 Release Notes

Release 2.3.1 is a Beta release.

This document describes the changes in release 2.3.1, when compared to release 2.3.0.

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

Changed Features

Binlog Router

Secondary masters can now be specified also when file + position based replication is used. Earlier it was possible only in conjunction with GTID based replication.

mmmon and ndbclustermon

Both of these modules have been deprecated and will be removed in a future release. The functionality in mmmon has been largely obsoleted by the advancements in mariadbmon. The ndbclustermon is largely obsolete due to the fact that there are virtually no users who use it.

Deprecated options

The following configuration file options have been deprecated and will be removed in 2.4.

Global section

  • non_blocking_polls, ignored.
  • poll_sleep, ignored.
  • thread_stack_size, ignored.

Services and Monitors

  • passwd, replaced with password.

MaxAdmin

The commands set pollsleep and set nbpolls have been deprecated and will be removed in 2.4.

New Features

MaxCtrl

There is now a new command classify <statement> using which it can be checked if and how MaxScale classifies a specific statement. This feature can be used for debugging, if there is suspicion that MaxScale sends a particular statement to the wrong server (e.g. to a slave when it should be sent to the master).

Bug fixes

Here is a list of bugs fixed in MaxScale 2.3.1.

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