dcf53da209
Enabling the feature by default prevents the master connection from dying during times when there are very little or no writes. Having a modest ping interval of 300 seconds serves to minimize the amount of extra work that both MaxScale and the server have to do while still keeping the connections in good shape.
48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# MariaDB MaxScale 2.3.2 Release Notes
|
|
|
|
Release 2.3.2 is a XXX release.
|
|
|
|
This document describes the changes in release 2.3.2, when compared to the
|
|
previous release in the same series.
|
|
|
|
For any problems you encounter, please consider submitting a bug
|
|
report on [our Jira](https://jira.mariadb.org/projects/MXS).
|
|
|
|
## Changed Features
|
|
|
|
### Watchdog
|
|
|
|
The systemd watchdog is now safe to use in all circumstances.
|
|
|
|
By default it is enabled with a timeout of 60 seconds.
|
|
|
|
### Readwritesplit
|
|
|
|
#### `connection_keepalive`
|
|
|
|
The default value of `connection_keepalive` is now 300 seconds. This prevents
|
|
the connections from dying due to wait_timeout with longer sessions. This is
|
|
especially helpful with pooled connections that stay alive for a very long time.
|
|
|
|
## Bug fixes
|
|
|
|
## Known Issues and Limitations
|
|
|
|
There are some limitations and known issues within this version of MaxScale.
|
|
For more information, please refer to the [Limitations](../About/Limitations.md) document.
|
|
|
|
## Packaging
|
|
|
|
RPM and Debian packages are provided for supported the Linux distributions.
|
|
|
|
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
|
|
|
|
## 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`. Further, the default branch is always the latest GA version
|
|
of MaxScale.
|
|
|
|
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|