# MaxScale 25.01 Changelog

<table data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td align="center"><p><strong>WEBINAR</strong></p><p>New innovations in MaxScale 25.01 and Enterprise Platform</p></td><td align="center"><a href="https://go.mariadb.com/WBN-Real-world-testing-with-MariaDBEnterprisePlatform-2025-02-28_Registration-LP.html?utm_source=onpagepromo&#x26;utm_medium=kb&#x26;utm_campaign=webinar-maxscale-25-01"><strong>Watch Now</strong></a></td><td><a href="https://go.mariadb.com/WBN-Real-world-testing-with-MariaDBEnterprisePlatform-2025-02-28_Registration-LP.html?utm_source=onpagepromo&#x26;utm_medium=kb&#x26;utm_campaign=webinar-maxscale-25-01">https://go.mariadb.com/WBN-Real-world-testing-with-MariaDBEnterprisePlatform-2025-02-28_Registration-LP.html?utm_source=onpagepromo&#x26;utm_medium=kb&#x26;utm_campaign=webinar-maxscale-25-01</a></td><td><a href="broken-reference">Broken file</a></td></tr></tbody></table>

* The functionality that was enabled by the `reuse_prepared_statements` parameter in readwritesplit has been moved into the [PsReuse](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-filters/mariadb-maxscale-2501-maxscale-2501-psreuse) filter module. The `reuse_prepared_statements` parameter has been removed from readwritesplit.
* The functionality that was enabled by the `optimistic_trx` parameter in readwritesplit has been moved into the [OptimisticTrx](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-filters/mariadb-maxscale-2501-maxscale-2501-optimistic-transaction-execution-filter) filter module. The`optimistic_trx` parameter has been removed from readwritesplit.
* Added a safe-option to MariaDB Monitor auto-failover. safe does not perform failover if data loss is certain. Equivalent manual command added. See [monitor documentation](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-2501-maxscale-25-01-monitors/mariadb-maxscale-2501-maxscale-2501-mariadb-monitor) for more information. This change affects REST-API output: the *attributes.parameters.auto\_failover*-field of the monitor JSON description is now a string.
* MariaDB Monitor can perform a write test on the primary server. See [monitor documentation](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-2501-maxscale-25-01-monitors/mariadb-maxscale-2501-maxscale-2501-mariadb-monitor) for more information.
* MariaDB Monitor switchover can be called with key-value arguments. This form also supports leaving the old primary in maintenance mode instead of redirecting it. See [monitor documentation](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-2501-maxscale-25-01-monitors/mariadb-maxscale-2501-maxscale-2501-mariadb-monitor) for more information.
* Allowed REST-API TLS ciphers can be tuned with the global setting [admin\_ssl\_cipher](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-getting-started/mariadb-maxscale-2501-maxscale-2501-mariadb-maxscale-configuration-guide#admin_ssl_cipher).
* The `transaction_replay_safe_commit` parameter in readwritesplit now also disables the replaying of all writes done when autocommit is enabled. This means that transaction replay will never replay a statement that may commit a transaction.
* NoSQL protocol has been extended.
* Now supports [MongoDB Compass](https://www.mongodb.com/products/tools/compass)
* Initial support for the command aggregate has been added.
* When running in a container, MaxScale adapts to the amount of resources available in the container.
* MaxGUI Query Editor now requires delimiter changes for compound statements such as stored procedures, functions, etc. See [delimiters documentation](https://app.gitbook.com/s/SsmexDFPv2xG2OTyO5yV/clients-and-utilities/mariadb-client/delimiters) for more information. However, the dedicated SQL editor (opened via "Create Function", "Alter Function", "Create Trigger" etc., in the schema tree explorer) does not require delimiter changes as it handles SQL as a single statement.
* MaxGUI Query Editor now automatically injects a `LIMIT` clause with a default limit of 10000 into every `SELECT` statement.
* The new [trace\_file\_dir](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-getting-started/mariadb-maxscale-2501-maxscale-2501-mariadb-maxscale-configuration-guide#trace_file_dir) and [trace\_file\_size](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-getting-started/mariadb-maxscale-2501-maxscale-2501-mariadb-maxscale-configuration-guide#trace_file_size) parameters can be used to enable a trace log that writes messages from all log levels to a set of rotating log files. If enabled, the symlink`/var/log/maxscale/maxscale.trace` will point to the latest trace log file. This is a low-overhead alternative to enabling `log_info` and is intended to be used for debugging application problems in production where the overhead of `log_info` cannot be afforded.
* The [Avro Router](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-routers/mariadb-maxscale-2501-maxscale-2501-avrorouter) and the [CDC Protocol](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-protocols/mariadb-maxscale-2501-maxscale-2501-change-data-capture-cdc-protocol) have been deprecated and will be removed in the next major release.[KafkaCDC](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-routers/mariadb-maxscale-2501-maxscale-2501-kafkacdc) can be used instead.
* The [passive](https://app.gitbook.com/s/0pSbu5DcMSW4KwAkUcmX/maxscale-archive/archive/mariadb-maxscale-25-01/mariadb-maxscale-25-01-getting-started/mariadb-maxscale-2501-maxscale-2501-mariadb-maxscale-configuration-guide#passive) configuration setting has been deprecated and will be removed in the next series.

For more details, please refer to:

* [MariaDB MaxScale 25.01.6 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.6)
* [MariaDB MaxScale 25.01.5 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.5)
* [MariaDB MaxScale 25.01.4 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.4)
* [MariaDB MaxScale 25.01.3 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.3)
* [MariaDB MaxScale 25.01.2 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.2)
* [MariaDB MaxScale 25.01.1 Release Notes](https://mariadb.com/docs/release-notes/maxscale/25.01/25.01.1)

The changelog for the previous MaxScale version can be found [here](https://mariadb.com/docs/release-notes/maxscale/24.02/24.02-changelog).

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

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