MaxScale 25.10.3 Release Notes

Release 25.10.3 is a GA release.

Release Date: 15 Jun 2026

This document describes the changes in release 25.10.3, 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 for this MaxScale version.

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

New Packages

Although a maintenance release, MaxScale 25.10.3 introduces some significant new functionality that, in order to not change the dependencies of exiting packages, are delivered in packages of their own.

maxscale-exasol

Contains exasolrouter, a MaxScale router that is capable of routing requests to an Exasol Analytics Engine.

maxscale-maxctrl2

Contains a reimplemenation of maxctrl. The primary differences to maxctrl are

• implemented in C++, so there is no dependency on node.js anymore, and

• provides TAB-completion, which makes interactive use significantly simpler.

Otherwise it is intended to be functionally equivalent with maxctrl.

New Features

• MXS-6596 tabular output in ASCII (in 25.10.3-2, concerns maxscale-maxctrl2)

• MXS-6594 show the table headers if --tsv is used (in 25.10.3-2, concerns maxscale-maxctrl2)

• MXS-6284 Support of prepared statements in the diff router

• MXS-6261 Exasol cdc write gtid to exasol for crash recovery

• MXS-6260 exasol cdc to write GTID

• MXS-6259 Include python & sqlglot dependencies with exasol router package and implement runtime

• MXS-6258 Exasol router as its own package

• MXS-6257 Exasol cdc handle datatype conversions

• MXS-6256 Exasol cdc create table

• MXS-6251 Bundle exasol odbc connector in maxscale

• MXS-6221 Gridgain as Cache storage

• MXS-6094 maxctrl or the REST API command to get connected slave hosts to the binlogrouter

• MXS-4553 Rewrite maxctrl

Bug fixes

• MXS-6606 mxq::ODCB::disconnect() disconnects/frees handles in the wrong order (in 25.10.3-2, relevant for maxscale-exasol)

• MXS-6579 X-HTTP-Method-Override header allows a basic user to perform admin operations

• MXS-6576 Sysbench test fails vs exasol router (in 25.10.3-2, concerns maxscale-exasol)

• MXS-6566 lower_case_table_names breaks kafkacdc replication

• MXS-6564 trace_file_dir creates directory with inadequate permissions

• MXS-6563 Connection unexpectedly closed if server dies after a transaction

• MXS-6536 Configuration synchronization performance regression

• MXS-6508 COM_RESET_CONNECTION doesn't clear out session command history

• MXS-6494 Confusing 'Need DNS lookup' status on startup with IP addresses

• MXS-6463 Cooperative monitoring can lose exclusive locks if a server is slow to respond

• MXS-6462 MaxScale 25 does not allow 'type=basic' users run 'maxctrl list users' command

• MXS-6461 causal_reads=universal uses only the first GTID domain from the GTID list

• MXS-6420 Using a shared storage with threading model thread_specific causes crash

• MXS-6392 Bulk results do not work as expected

• MXS-6381 ssl operations fail from certain apps

• MXS-6374 MariaDB Monitor does not properly verify its configuration when performing runtime modifications

• MXS-6367 session_trace is always set to 1 if enabled

• MXS-6366 MaxScale fails to start on upgrade if deprecated options are in the db config table.

• MXS-6365 event_authentication_failure_level=LOG_EMERG does not produce log output on auth failure

• MXS-6305 REST-API shouid send the Strict-Transport-Security header if HTTPS is used

• MXS-6304 Missing Content-Type header for authentication failure responses

• MXS-6301 MaxScale upgrade to 25.10 not removing older version packages in Suse Linux SLES 15

• MXS-6291 Wrong configuration name in deprecation warning for event.authentication_failure.level

• MXS-6283 MaxScale Crash (Signal 6) in Replicator during Partition DDL (Truncate/Add Partition)

• MXS-6281 No header printed for log_data=command

• MXS-6280 maxvisualize with empty queries array results in errors

• MXS-6265 maxctrl call command executed for Reset-Replication we are seeing timeout error, But operation is successful.

• MXS-6238 Cluster config sync - dont sync active/passive

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 supported Linux distributions.

Packages can be downloaded here.

_{This page is: Copyright © 2025 MariaDB. All rights reserved.}