> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/release-notes/maxscale/26.10/26.10.0.md).

# MaxScale 26.10.0 Release Notes

MaxScale 26.10.0 is a Stable (GA) release of MariaDB MaxScale 26.10, released on 2026-11-03

**Release date:** 3 Nov 2026

Release 26.10.0 is a GA release.

This document describes the changes in release 26.10, when compared to release 25.10.

If you are upgrading from an older major version of MaxScale, please read the [upgrading document](/docs/maxscale/maxscale-management/deployment/upgrading-maxscale.md) for this MaxScale version.

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

## Changed Features

### [MXS-6274](https://jira.mariadb.org/browse/MXS-6274) MaxScale requires a license key

MaxScale 26.10 does not start without a valid license key in the `license_key` setting under the `[maxscale]` section. Earlier versions required a license key only for MaxScale Trial. A production license key and a trial license key both work. Get a key from the [MariaDB License Portal](https://customers.mariadb.com/license/).

When upgrading from 25.10 or earlier, stop MaxScale before you upgrade the packages, and add the key before you start MaxScale 26.10. See [Upgrading MaxScale](/docs/maxscale/maxscale-management/deployment/upgrading-maxscale.md#license-key-required) and [Install a MaxScale License Key](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-license-key.md).

### [MXS-6550](https://jira.mariadb.org/browse/MXS-6550) ISO 8601 timestamps in MaxScale log messages

Log messages now use a ISO 8601 timestamp which is a standardized, easy to parse time format that includes the UTC timezone offset for easier cross-region log analysis. To use the old legacy timestamp format, add `log_timestamp_format=datetime` under the `[maxscale]` section. By default, a warning is logged on startup for existing installations. To silence it, add `log_timestamp_format=iso_8601` under the `[maxscale]` section.

See [`log_timestamp_format`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide/global-settings.md#log_timestamp_format) for more information.

### [MXS-6239](https://jira.mariadb.org/browse/MXS-6239) A passive MaxScale no longer takes cooperative monitoring locks

If the MariaDB Monitor setting [cooperative\_monitoring\_locks](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#cooperative_monitoring_locks) is used with `passive=true`, the monitor will no longer acquire any locks, and it releases any locks it holds. The monitor will assume that another MaxScale will acquire the locks and select a primary server. If all MaxScales are passive, no server is designated primary, so at least one MaxScale must be active.

## Dropped Features

### [MXS-7620](https://jira.mariadb.org/browse/MXS-7620) Memcached no longer supported as storage for cache

Memcached is no longer supported as storage for the MaxScale Cache.

### [MXS-7582](https://jira.mariadb.org/browse/MXS-7582) Avrorouter no longer supported

The avrorouter module which was deprecated in MaxScale 25.01 has been removed in MaxScale 26.10. The kafkacdc module is a more efficient and flexible approach that solves the same problem using an industry standard kafka broker.

## Deprecated Features

### [MXS-6538](https://jira.mariadb.org/browse/MXS-6538) MariaDB Monitor setting assume\_unique\_hostnames is deprecated

Use server setting [private\_address](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#private_address) instead.

## New Features

### [MXS-7647](https://jira.mariadb.org/browse/MXS-7647) NoSQL supports the MongoDB wire protocol of recent clients

The NoSQL protocol module now supports versions up to 9 of the MongoDB wire protocol, which recent clients, such as mongosh 2.13.0, require. Transactions are not supported, and a new transactions setting controls what happens when a client attempts to use them.

See [transaction support](/docs/maxscale/reference/maxscale-protocols/maxscale-nosql-protocol-module.md#transaction-support) for more information.

### [MXS-7561](https://jira.mariadb.org/browse/MXS-7561) Readwritesplit synchronizes transactions while the primary is throttled

Readwritesplit automatically enables `sync_transaction` if the current primary server is being throttled. Once throttling stops, `sync_transaction` is disabled. See [sync\_transaction\_throttle\_rate](/docs/maxscale/reference/maxscale-routers/maxscale-readwritesplit/readwritesplit-settings.md#sync_transaction_throttle_rate) for more information.

### [MXS-6921](https://jira.mariadb.org/browse/MXS-6921) Arbitrator servers for cooperative monitoring in MariaDB Monitor

MariaDB Monitor now supports [cooperative\_monitoring\_arbitrator\_nodes](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#cooperative_monitoring_arbitrator_nodes). Arbitrator nodes are only used for cooperative monitoring locks and most routers will not route SQL traffic to them.

### [MXS-6820](https://jira.mariadb.org/browse/MXS-6820) Export service metrics via OpenTelemetry and count errors per target

Service level metrics, such as routed packets, errors and transactions, are now exported via OpenTelemetry, which makes it possible to monitor services that act as servers, for example the Exasol router. Errors are now counted for every target that returns one, including the replies to queries that are sent to several targets, instead of only for the reply that is returned to the client.

### [MXS-6781](https://jira.mariadb.org/browse/MXS-6781) Start and stop replication to Exasol at runtime

Exasol CDC is now started and stopped with the binlogrouter module commands `cdc-start` and `cdc-stop`, without restarting MaxScale. Stopping it does not affect the replication of the binlogrouter itself, and whether it is running is remembered over restarts. A new Exasol CDC is stopped until `cdc-start` is run. See [Starting and Stopping](/docs/maxscale/reference/maxscale-routers/maxscale-exasol-cdc.md#starting-and-stopping) for more information.

### [MXS-6772](https://jira.mariadb.org/browse/MXS-6772) For selected tables, keep data in Exasol when it is deleted in MariaDB

The new Exasol CDC setting `odbc_insert_only_tables` lists tables whose data is kept in Exasol when it is deleted in MariaDB. Inserts and updates to these tables are replicated, but deletes are not, and neither are `TRUNCATE TABLE`, `DROP TABLE` or `ALTER TABLE ... DROP COLUMN`. See [odbc\_insert\_only\_tables](/docs/maxscale/reference/maxscale-routers/maxscale-exasol-cdc.md#odbc_insert_only_tables) for more information.

### [MXS-6765](https://jira.mariadb.org/browse/MXS-6765) MariaDB Monitor can heal a primary that lost transactions in a crash

MariaDB Monitor can heal a primary server that has truncated its binary logs during crash recovery. See [here](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#heal_primary_truncated_binlog) for more information.

### [MXS-6764](https://jira.mariadb.org/browse/MXS-6764) Configurable schedule for re-measuring queries in SmartRouter

The smartrouter performance info eviction schedule is now configurable with a custom schedule with the [eviction\_schedule](/docs/maxscale/reference/maxscale-routers/maxscale-smartrouter.md#eviction_schedule) setting.

### [MXS-6612](https://jira.mariadb.org/browse/MXS-6612) Replicate MariaDB users, roles and grants to Exasol

With the new Exasol CDC setting `odbc_manage_user_grants`, `CREATE USER`, `DROP USER`, `CREATE ROLE`, `DROP ROLE`, `GRANT` and `REVOKE` are replicated to Exasol. The privileges are mapped to their Exasol equivalents, and those without one are ignored. See [Replicating Users](/docs/maxscale/reference/maxscale-routers/maxscale-exasol-cdc.md#replicating-users) for more information.

### [MXS-6593](https://jira.mariadb.org/browse/MXS-6593) Route SmartRouter reads to a chosen cluster with hints

SmartRouter now supports the routing hints of the hintfilter, which make it possible to route a read to a particular cluster instead of the one SmartRouter would select, for example to compare the clusters or to query the analytical cluster directly. Only hints that route to the master or to a named target are supported, and writes and statements inside transactions are not affected by hints. A hinted query does not affect the performance information that SmartRouter uses for selecting the cluster.

### [MXS-6572](https://jira.mariadb.org/browse/MXS-6572) Throttle writes to a server until replication catches up

Writes to servers in MaxScale can now be throttled with the `maxctrl set server <name> throttle` command. If a readwritesplit service uses a server that's being throttled, it will add a linearly increasing delay to each COMMIT until replication lag catches up after which transactions proceed as fast as the replicas can process.

### [MXS-6514](https://jira.mariadb.org/browse/MXS-6514) Readwritesplit releases connections to drained servers sooner

Readwritesplit now more aggressively releases connections to servers that are being drained. The readwritesplit feature where it drops connections to severely lagging servers also now deals with idle connections to those servers. Idle connections to servers being drained or to servers in maintenance mode now drop connections even without the `--force` option.

### [MXS-6513](https://jira.mariadb.org/browse/MXS-6513) The primary can be put in maintenance or drained with --force

Servers can now be set to maintenance and drain modes even if they're labeled as `Write` by the monitor if the `--force` flag is used.

### [MXS-6383](https://jira.mariadb.org/browse/MXS-6383) MaxScale uses TLS to servers that support it, by default

If a server is configured with `ssl=allow`, MaxScale uses TLS if server supports it, but falls back to unencrypted connections if not. See [configuration guide](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#tls-ssl-encryption) for more information.

`ssl=allow` is the new default value, which means MaxScale defaults to encrypted backend connections if available. This can increase CPU usage slightly. To disable encryption for backend connections, set `ssl=disable` for each server.

### [MXS-6294](https://jira.mariadb.org/browse/MXS-6294) Export MaxScale logs via OpenTelemetry

MaxScale now also exports all log messages via OpenTelemetry if it has been configured to export telemetry. The new [`telemetry_signals`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide/global-settings.md#telemetry_signals) configuration setting controls which signals are sent. By default, both metrics and logs are sent. The [`telemetry_url`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide/global-settings.md#telemetry_url) is now interpreted as the base URL where the telemetry is sent. The metrics and logs endpoints can also be configured with the [`telemetry_metrics_url`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide/global-settings.md#telemetry_metrics_url) and [`telemetry_logs_url`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide/global-settings.md#telemetry_logs_url) in case they're not being sent to the same location.

### [MXS-6264](https://jira.mariadb.org/browse/MXS-6264) Copy existing MariaDB data and users into Exasol

An existing MariaDB database can now be copied into Exasol before Exasol CDC starts replicating, with `cdc-start <service> bulk-copy=<file>`. The copy creates the tables in Exasol and copies their rows, and replication then continues from the position at which the copy was made. The users and roles of a MariaDB server can be copied into Exasol, with their grants, with the module command `cdc-copy-users`. See [Bulk Copy](/docs/maxscale/reference/maxscale-routers/maxscale-exasol-cdc.md#bulk-copy) and [Copying Users](/docs/maxscale/reference/maxscale-routers/maxscale-exasol-cdc.md#copying-users) for more information.

### [MXS-6262](https://jira.mariadb.org/browse/MXS-6262) Causal reads with SmartRouter

The SmartRouter now supports `causal_reads`, similarly as ReadWriteSplit although with some differences as the intent of SmartRouter is that it routes to servers that can have very different performance characteristics. The ExasolRouter provides the information needed by SmartRouter so causal reads with SmartRouter routing writes to MariaDB and some reads to Exasol is now supported.

See [causal\_reads](/docs/maxscale/reference/maxscale-routers/maxscale-smartrouter.md#causal_reads) for more information.

### [MXS-6237](https://jira.mariadb.org/browse/MXS-6237) Sort query statistics by hits, last use or duration

The `/v1/maxscale/query_classifier/cache` REST-API endpoint now supports a `sort` option that takes either `hits` which is the default and sorts by the most frequently used query, `last_used` which sorts by the most recently used query or by `duration` which sorts queries by the sum of their execution time.

### [MXS-6233](https://jira.mariadb.org/browse/MXS-6233) MariaDB Monitor keeps replication from an external cluster working when its primary changes

MariaDB Monitor supports external replication management by relying on the results of another monitor. This allows the monitor to update the external replication connection if the external primary goes down or its role changes. See [MariaDB Monitor documentation](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor.md#external-replication-management) for more information.

### [MXS-6226](https://jira.mariadb.org/browse/MXS-6226) New router for running SQL on a GridGain cluster

GridGainRouter is a new router that runs the statements it receives on a GridGain cluster using ODBC. The cluster is specified with the `odbc_connection_string` setting, and the statements are sent to GridGain as they are, so they must be valid in the SQL of GridGain. Optionally, a MariaDB server or service can be given as a target, in which case it is used only for authenticating clients. The router can also be used as a target of SmartRouter. A client must specify a default schema when it connects, and the schema cannot be changed during the session.

See [GridGain Router](/docs/maxscale/reference/maxscale-routers/maxscale-gridgainrouter.md) for more information.

### [MXS-6102](https://jira.mariadb.org/browse/MXS-6102) A busy server is not marked down when only the monitor times out

A monitored server may remain in running status if the connection failure was due to connection timeout and if MaxScale has recently received data from the server in response to a client query. These conditions suggest that the server is still running, but too busy to process MaxScale monitor connections.

### [MXS-6090](https://jira.mariadb.org/browse/MXS-6090) Debug symbols in a separate package

MaxScale 26.10 now ships debug symbols in a separate package.

### [MXS-6010](https://jira.mariadb.org/browse/MXS-6010) One listener for several services, chosen by TLS SNI

Listeners now support [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication). SNI allows a client to connect to different MaxScale services through one listener. MaxScale can select a TLS certificate depending on the host the client is connecting to. This feature is configured with an external JSON file. See [listener documentation](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#sni_mapping_file) for more information.

### [MXS-6000](https://jira.mariadb.org/browse/MXS-6000) The REST API can download the MariaDB ODBC driver

The new `/v1/sql/odbc/drivers/install` endpoint downloads the MariaDB ODBC driver version 3.2.9 or newer. If no specific version is requested, the latest version is downloaded. The downloaded drivers are listed in the `/v1/sql/odbc/drivers` endpoint so that they are exposed in the API and make it possible to use them without access to the filesystem.

### [MXS-5999](https://jira.mariadb.org/browse/MXS-5999) Query log events can be sent to Kafka

The QLA Filter now supports sending log events to Kafka. See [QLAFilter documentation](/docs/maxscale/reference/maxscale-filters/maxscale-query-log-all-filter.md) for more information.

### [MXS-5990](https://jira.mariadb.org/browse/MXS-5990) MaxScale sends the server name (SNI) in TLS connections to servers

MaxScale now sets the TLS SNI for encrypted connections to MariaDB.

### [MXS-5975](https://jira.mariadb.org/browse/MXS-5975) Separate log events for session start and end

New log event types have been added for new sessions and closed sessions which can be controlled with the following settings:

* [`event_session_start_level`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#session_start)
* [`event_session_start_facility`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#session_start)
* [`event_session_stop_level`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#session_stop)
* [`event_session_stop_facility`](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#session_stop)

### [MXS-5768](https://jira.mariadb.org/browse/MXS-5768) Query latency percentiles per server

MaxScale now tracks query latency percentiles per server. These are available in the REST-API at `/v1/maxscale/query_classifier/cache/` and with `maxctrl show query_statistics`.

### [MXS-5609](https://jira.mariadb.org/browse/MXS-5609) MaxGUI shows mandatory parameters first and can show only them

In MaxGUI, parameter lists now show the mandatory parameters first. They can still be sorted in ascending or descending order. The new `Show required only` switch hides all other parameters, and its setting is remembered.

### [MXS-5594](https://jira.mariadb.org/browse/MXS-5594) A listener can accept both encrypted and unencrypted connections

A listener now accepts encrypted and unencrypted connections if configured with `ssl=allow`. See [configuration guide](/docs/maxscale/maxscale-management/deployment/installation-and-configuration/maxscale-configuration-guide.md#tls-ssl-encryption) for more information.

The `ssl` setting of listeners and servers is now an enumeration with the values `disable`, `allow` and `require`, of which `allow` is the default. The old boolean values are still accepted: `true` means `require` and `false` means `disable`. In the REST API, the `ssl` field of listeners and servers is now a string instead of a boolean.

### [MXS-5555](https://jira.mariadb.org/browse/MXS-5555) Switchover waits for open transactions to finish

Mariadbmon now waits for open transactions from readwritesplit to close before proceeding with a switchover. This makes switchovers a lot less disruptive. With `delayed_retry=true` in readwritesplit, switchovers should be completely invisible under normal conditions. See [switchover\_wait\_for\_trx](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#switchover_wait_for_trx) for more information.

### [MXS-5375](https://jira.mariadb.org/browse/MXS-5375) Stop and start listeners in MaxGUI

Listeners can now be stopped and started on their detail page in MaxGUI, as services and monitors already could.

### [MXS-5335](https://jira.mariadb.org/browse/MXS-5335) Diagnostic report for MariaDB support in MaxGUI

MaxGUI has a new Report page that collects the state of MaxScale into one JSON document: MaxScale itself, its servers, services, monitors, listeners, filters, sessions and threads, diagnostics of the servers, and the latest lines of the MaxScale log. The report can be searched and filtered, and exported as a file to attach to a MariaDB support case.

### [MXS-4819](https://jira.mariadb.org/browse/MXS-4819) Galera Monitor keeps replication from an external cluster working when its primary changes

Galera Monitor supports external replication management by relying on the results of another monitor. This allows the monitor to update the external replication connection if the external primary goes down or its role changes. See [Galera Monitor documentation](/docs/maxscale/reference/maxscale-monitors/galera-monitor.md#external-replication-management) for more information.

### [MXS-3577](https://jira.mariadb.org/browse/MXS-3577) MariaDB Monitor preserves the MASTER\_SSL setting of replication

MariaDB Monitor config setting `replication_master_ssl` now supports the `auto`-value, which causes the monitor to preserve the existing value of MASTER\_SSL. `auto` is also the new default; previously the default was `false`. In the REST API, the `replication_master_ssl` field of the monitor parameters is now a string instead of a boolean. See [monitor documentation](/docs/maxscale/reference/maxscale-monitors/mariadb-monitor/mariadb-monitor-settings.md#replication_master_ssl) for more information.

## Bug fixes

* [MXS-7652](https://jira.mariadb.org/browse/MXS-7652) Maxscale GUI shows red ! when replication is working
* [MXS-7581](https://jira.mariadb.org/browse/MXS-7581) Review the default Restart setting in the MaxScale systemd service configuration
* [MXS-7576](https://jira.mariadb.org/browse/MXS-7576) Query against Exasol hangs when the result set has a large VARCHAR and a TIMESTAMP
* [MXS-6884](https://jira.mariadb.org/browse/MXS-6884) Persistent connection pool statistics are not exported via OpenTelemetry
* [MXS-6862](https://jira.mariadb.org/browse/MXS-6862) Exasol router emitting wrong column-definition packets
* [MXS-6746](https://jira.mariadb.org/browse/MXS-6746) Queries from smartrouter don't count towards active operation count
* [MXS-6742](https://jira.mariadb.org/browse/MXS-6742) Smartrouter aborts session when queries are pipelined
* [MXS-6701](https://jira.mariadb.org/browse/MXS-6701) KILL USER doesn't kill a user with spaces in the username
* [MXS-6289](https://jira.mariadb.org/browse/MXS-6289) Change log level to warning for replay checksum errors

## Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the [Limitations](/docs/maxscale/maxscale-management/mariadb-maxscale-limitations-guide.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).

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

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