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

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• Network options for maxvisualize are not documented

• maxpostprocess install failure leaves a corrupt installation

• Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

• The logout screen is shown when accessing the MaxGUI login view.

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the guide.

Packaging

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

Packages can be downloaded .

Release 25.01.5 is a GA release.

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

If you are upgrading from an older major version of MaxScale, please read the for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

• No error message if connection to server fails during start of switchover

• SHOW CREATE TABLE doesn't detect if a temporary table is used

• Signal 11 crash

• Default users_refresh_interval causes repeated user account loading

• maxctrl create report --archive error reporting produces errors

• kafkacdc doesn't escape db name identifiers resulting in errors

• MaxScale failover fails with MASTER_SSL=1 default in MariaDB 11.4

• Database names with dashes are not properly escaped when disabling events

• Fix for MXS-5196 can break "maxctrl create report"

• MaxKeys usage message is obsolete

• Rebuild Replica fails when using MaxScale encrypted password for monitor user

• MariaDBMon should not solely depend on "STOP SLAVE" when doing failover/switchover

• ssl_ciphers-setting does not affect TLSv1.3 ciphers

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the document.

Packaging

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

Packages can be downloaded .

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

If you are upgrading from an older major version of MaxScale, please see .

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

• Role-based result row limit in Query Editor

Bug fixes

• MaxCtrl/REST-API should tell if password encryption is enabled

• MaxScale 24.02.6 is not compatible with MariaDB 12.0.2: Monitor fails with 'Cannot convert field ON to boolean'

• Upgrade Connector/C to 3.3.16 and 3.4.6

• Error 1047 when trying to run semi-sync replication through Maxscale

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the guide.

Packaging

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

Packages can be downloaded .

• The functionality that was enabled by the reuse_prepared_statements parameter in readwritesplit has been moved into the 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 filter module. Theoptimistic_trx parameter has been removed from readwritesplit.

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

If you are upgrading from an older major version of MaxScale, please see Upgrading MaxScale.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

• Fixed by Update avro-c to 1.11.4

Bug fixes

• kafkacdc commits offsets when it probes GTIDs from Kafka

• Logs Archive page doesn't show useful API error

• Not all parameters are shown when creating a new object in the GUI

• maxpostprocess and maxvisualize do not work when used from a binary tarball

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the guide.

Packaging

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

Packages can be downloaded .

This document describes the changes in release 25.01, when compared to release 24.02.

For any problems you encounter, please consider submitting a bug report on our Jira.

Changed Features

Scale everything according to the amount of available container resources

If MaxScale is running in a container, it will adapt to amount of resources (CPUs and memory) available in the container. See and for more information.

Dropped Features

Deprecated Features

New Features

Fully support inclusion and exclusion in projection document of find

now supports the exclusion of any field and not only _id. Further, fields can also be added and the value of an existing field reset using expressions.

Diff - Router for comparing different servers

Diff is a router using which the behaviour of two servers can be compared. Please see for more information.

Workload Capture and Replay

A number of components using which a live workload can be captured and later replayed. Please see for more information.

Safe failover and safe auto_failover

Added a safe-option to MariaDB Monitor auto-failover. safe does not perform failover if data loss is certain. Equivalent manual command added. See for more information.

Add admin_ssl_cipher setting

Enabled REST-API TLS ciphers can be tuned with the global setting .

Add low overhead trace logging

The new and parameters can be used to enable a trace log that writes messages from all log levels to a set of rotating log files.

This feature is an alternative to enabling which is not always feasible in a production system due to the high volume of log data that it creates. This overhead of writing large amounts of trace logging data could be mitigated by placing the log directory on a volatile in-memory filesystem but this risks losing important warning and error messages if the system were to be restarted.

The new trace logging mechanism combines the best of both worlds by writing the normal log messages to the MaxScale log while also writing the info level log messages into a separate set of rotating log files. This way, the important messages are kept even if the system is restarted while still allowing the low-level trace logging to be used to analyze the root causes of client application problems.

Add support for MongoDB Compass

now implements the commands needed by , which now can be used for browsing NoSQL collections.

Track reads and writes at the server level

In addition to the existing routed_packets counter in the service and server statistics, the number of reads and writes is also tracked with the new routed_writes and routed_reads counters.

Don't replay autocommit statements with transaction_replay

With transaction_replay_safe_commit=true (the default), readwritesplit will no longer replay statements that were executed with autocommit=1. This means that a statement like INSERT INTO software(name) VALUES ('MariaDB') will not be replayed if it's done outside of a transaction and its execution was interrupted. This feature makes transaction_replay safer by default and avoids duplicate execution of statements that may commit a transaction.

Test primary server writability in MariaDB Monitor

MariaDB Monitor can perform a write test on the primary server. Monitor can be configured to perform a failover if the write test fails. This may help deal with storage engine or disk hangups. See for more information.

Implement host_cache_size in MaxScale

Similar to MariaDB, MaxScale now stores the last 128 hostnames returned by reverse name lookups. This improves the performance of clusters where clients are authenticated based on a hostname instead of a plain IP address. The new parameter can be used to control the size of the cache and the cache can be disabled with host_cache_size=0.

support bulk returning all individual results

MaxScale now supports the protocol extensions added in MariaDB 11.5.1 where the bulk execution of statements returns multiple results.

Add switchover option which leaves old primary server to maintenance mode

MariaDB Monitor module command switchover can now be called with key-value arguments. This form also supports leaving the old primary in maintenance mode instead of redirecting it. See for more information.

Extend the number of supported aggregation stages and operations.

now implements the command and provides a number of aggregation pipe line and .

MaxGUI

Numerous additions have been added and improvements made to MaxGUI. The most notable ones are listed here:

• Show Only SQL editor Sessions/Connections Status Separately On Maxscale GUI

• Auto-inject LIMIT and OFFSET, and allow no limit

• Auto expand active schema node

Bug fixes

These are bug-fixes, which are not present in MaxScale 24.02.4, the most recent MaxScale maintenance release.

• KafkaCDC JSON conversion is taking most of the CPU time

• SystemD complains about legacy PID file paths

• Kafkacdc may produce invalid JSON

• Resultset table not fully expanded for inactive query tab

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the guide.

Packaging

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

Packages can be downloaded .

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 .