# MaxScale 22.08.4 Release Notes

This document describes the changes in release 22.08.4, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the [upgrading document](https://mariadb.com/docs/maxscale/maxscale-versions/mariadb-maxscale-23-02/mariadb-maxscale-23-02-upgrading/mariadb-maxscale-2302-upgrading-mariadb-maxscale-from-6-to-2208) for\
this MaxScale version.

For any problems you encounter, please consider submitting a bug report on [our Jira](https://jira.mariadb.org/projects/MXS).

### Bug fixes

* [MXS-4476](https://jira.mariadb.org/browse/MXS-4476) Memory leak in smartrouter
* [MXS-4471](https://jira.mariadb.org/browse/MXS-4471) Table selection doesn't tolerate node failures
* [MXS-4470](https://jira.mariadb.org/browse/MXS-4470) COM\_INIT\_DB isn't routed to all shards
* [MXS-4469](https://jira.mariadb.org/browse/MXS-4469) Schemarouter routing logic documentation is out of date
* [MXS-4467](https://jira.mariadb.org/browse/MXS-4467) Explicit transactions without a default database do not work as expected with schemarouter
* [MXS-4460](https://jira.mariadb.org/browse/MXS-4460) Crash during query replay with service-to-service configuration
* [MXS-4454](https://jira.mariadb.org/browse/MXS-4454) Schemarouter should prefer targets which have databases in them for session commands
* [MXS-4453](https://jira.mariadb.org/browse/MXS-4453) Schemarouter selects an invalid target for queries that do not target a specific shard
* [MXS-4451](https://jira.mariadb.org/browse/MXS-4451) Memory issue in Maxscale
* [MXS-4450](https://jira.mariadb.org/browse/MXS-4450) 6.4 no longer provides full certificate chain in TLS HELLO
* [MXS-4442](https://jira.mariadb.org/browse/MXS-4442) MaxScale crashes when a certificate chain is used with the REST-API
* [MXS-4440](https://jira.mariadb.org/browse/MXS-4440) Lost connection to backend server: network error (server1: 104, Connection reset by peer)
* [MXS-4435](https://jira.mariadb.org/browse/MXS-4435) Log rotation causes errors in qlafilter
* [MXS-4434](https://jira.mariadb.org/browse/MXS-4434) SET STATEMENT variables are not ignored when statements are classified
* [MXS-4427](https://jira.mariadb.org/browse/MXS-4427) TLS reloading leaks memory
* [MXS-4423](https://jira.mariadb.org/browse/MXS-4423) Rebalancing is not always initiated from the affected worker/thread
* [MXS-4197](https://jira.mariadb.org/browse/MXS-4197) pinloki\_start\_stop is unstable
* [MXS-3972](https://jira.mariadb.org/browse/MXS-3972) The rpl\_state in binlogrouter is not atomic

### Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale.\
For more information, please refer to the [Limitations](https://github.com/mariadb-corporation/mariadb-docs/blob/main/release-notes/maxscale/mariadb-maxscale-2208-about/mariadb-maxscale-2208-limitations-and-known-issues-within-mariadb-maxscale.md) document.

### Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded [here](https://mariadb.com/downloads/#mariadb_platform-mariadb_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).

<sub>*This page is: Copyright © 2025 MariaDB. All rights reserved.*</sub>

{% @marketo/form formid="4316" formId="4316" %}