The Ultimate Guide to High Availability with MariaDB

MariaDB MaxScale 2.0.2 Release Notes

You are viewing an old version of this article. View the current version here.

MariaDB MaxScale 2.0.2 Release Notes

Release 2.0.2 is a GA release.

This document describes the changes in release 2.0.2, when compared to release 2.0.1.

If you are upgrading from release 1.4.4, please also read the release notes of release 2.0.0 and release 2.0.1.

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

Updated Features

MXS-978 Support for stale master in case of restart

In case where replication monitor gets a stale master status (slaves are down) and maxscale gets restarted, master loses the stale master status and no writes can happen.

To cater for this situation there is now a set server <name> stale command.

Bug fixes

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

  • MXS-1018: Internal connections don't use TLS
  • MXS-1008: MySQL Monitor with scripts leaks memory
  • MXS-976: Crash in libqc_sqlite
  • MXS-975: TCP backlog is capped at 1280
  • MXS-970: A fatal problem with maxscale automatically shut down
  • MXS-969: use_sql_variables_in=master can break functionality of important session variables
  • MXS-967: setting connection_timeout=value cause error : Not a boolean value
  • MXS-965: galeramon erlaubt keine TLS verschlüsselte Verbindung
  • MXS-960: MaxScale Binlog Server does not allow comma to be in password
  • MXS-957: Temporary table creation from another temporary table isn't detected
  • MXS-956: Removing DCB 0x7fbf94016760 but was in state DCB_STATE_DISCONNECTED which is not legal for a call to dcb_close
  • MXS-955: MaxScale 2.0.1 doesn't recognize user and passwd options in .maxadmin file
  • MXS-953: Charset error when server configued in utf8mb4
  • MXS-942: describe table query not routed to shard that contains the schema
  • MXS-917: False error message about master not being in use

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

Comments

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.