ce853d3f7f
Enabling the session command history but limiting it to a history of 50 commands allows reconnections for sessions that don't change the state too often. As pooled connections will exceed this limit quite fast, they are not able to reconnect to servers once connections are lost. To solve this problem, the session command history needs a compaction process that removes redundant history.
2.4 KiB
MariaDB MaxScale 2.3.0 Release Notes
Release 2.2.0 is a Beta release.
This document describes the changes in release 2.3.0, when compared to release 2.2.
For any problems you encounter, please consider submitting a bug report at Jira.
Changed Features
Session Command History
The readwritesplit session command history is now enabled mby default but it is limited to a total of 50 distict session commands. This default allows most sessions to leverage the newly improved reconnection mechanism without having to explicitly enable the history. When the limit of 50 commands is exceeded, the session command history is disabled. This makes it possible to use pooled connections by default without having to explicitly disable the history (this was the case with pre-2.1 versions of MaxScale).
The way that the history is stored has also changed. Instead of storing all session commands, each session only stores the first and last execution of each command. This way the history is compressed into a compact representation while still retaining the relative order of each command.
To keep the old functionality, add disable_sescmd_history=true to the service
definition.
Dropped Features
New Features
Runtime Configuration of the Cache
With the variable @maxscale.cache.enabled it is now possible for a
client to specify whether the cache should be used. Please see the
Cache documentation for details.
Bug fixes
Here is a list of bugs fixed in MaxScale 2.3.0.
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.