MariaDB MaxScale 25.10 Release Notes

WEBINAR
New innovations in MaxScale 25.01 and Enterprise Platform
The diagnostic output of
maxctrl show filternow shows the rules of a filter, if it has such.At startup, if there are filters that are not used by any service, or servers that are not referred to by any service or monitor, a warning will be logged.
net_write_timeoutnow also affects backend connections.The global settings
query_retryandquery_retry_timeout, as well as the monitor settingsbackend_write_timeoutandbackend_read_timeouthave been removed. The settings are still recognized but any configured values are ignored.The monitor setting
backend_connect_timeouthas been deprecated. Usebackend_timeoutinstead.Now possible to clear service and server statistics using maxctrl.
Support for compression protocols has been added to MaxScale. Both the traditional zlib compression as well as the newer zstd based compression protocols are supported by MaxScale.
MaxGUI Query Editor now disables logging for auto-generated queries by default, while queries manually written and executed in the Query Editor are still logged. Logging for both types can now be managed in the
Generaltab of thePreferencesdialog.MaxScale now uses Forward-confirmed reverse DNS whenever resolving client IP addresses to hostnames. This is similar to how MariaDB handles reverse DNS lookups. The
debug=disable-fcrdnsdebug option can be used to disable it in cases where there are issues with DNS servers.In the output of
maxctrl list server, the state of a server and reason for the state are now separated. The state of a server is shown asRead,Write,UporDown, possibly augmented withMaintenanceorDraining|Drained, while the reason for the state is shown in the next column.Added simple syntax for
maxctrl call commandthat allows object instances to be used in place of the module name. For example, themaxctrl call command mariadbmon switchover MariaDB-Monitorandmaxctrl call command MariaDB-Monitor switchoverare now both valid.Simple filters that have no settings are now automatically created by MaxScale whenever a service refers to them by the module name. For example,
filters=hintfilterwill enable routing hints for a service without having to define a separate filter section in the configuration.The statistics in readwritesplit and readconnroute that track session activity per backend have been replaced with a generic metric in the service that already tracked the average and maximum duration of a session. The
max_session_active_pctandavg_session_active_pcttrack the maximum and average percentage that a session has been active, that is, when a query has been in execution on a backend server. This can also be thought of as the length of the session with the idle subtracted from it. Themax_session_queriesandavg_session_queriestrack the maximum and average number of queries an individual session has done.MaxScale can now send metrics to an OpenTelemetry Collector. Telemetry configuration
Added scan-topology command to MariaDB Monitor.
Added discover-replicas command to both MariaDB Monitor and Galera Monitor.
Added bootstrap command to both MariaDB Monitor and Galera Monitor.
Added redirect command to MariaDB Monitor.
MariaDB Monitor backup commands (rebuild-server, create-backup, restore-from-backup) now support key-value arguments. The commands also support the dry-run-option, which checks if MaxScale configuration and servers support the commands.
MariaDB Monitor backup operation status can be shown in detail with the fetch-cmd-status command.
Available backups can be listed with the MariaDB Monitor list-backups command.
Added servers_no_cooperative_monitoring_locks setting to MariaDB Monitor.
Added auto_failback_switchover to MariaDB Monitor.
MaxCtrl now attempts to read the
[maxctrl]section from/etc/maxscale.cnfif the configuration file is present and readable. This can be used to customize the MaxCtrl options at a global level for all users.The
maxctrl create servercommand has a new--copyoption that uses the configuration of an existing server as the default configuration. This makes creating multiple similarly configured servers easier. For example,maxctrl create server server2 --copy server1 address=server2.my.host.comwould use the settings ofserver1forserver2but use a custom value for theaddresssetting.Galera Monitor now requires the
REPLICA MONITORprivilege and will fail to monitor the servers if lacking it. With MariaDB Server versions older than 10.5,REPLICATION CLIENTis required.It is now possible to dump the content of the query classifier cache using maxctrl.
Listeners and servers support zero-configuration SSL, as described here. See configuration guide for more information.
Added global setting require_secure_transport which forces encryption to be configured everywhere.
By default, MaxScale no longer generates a core file in case of a crash.
The system variable tracker value for
redirect_urlis intercepted and renamed by MaxScale tomxs_rdir_url. This is done to prevent accidental redirections away from MaxScale.The new redirect_url parameter can be used to implement connection redirection in MaxScale.
session_trace_matchis now matched for every logged message.When MaxScale is used with MariaDB 12 or later and the service user has the
SET USERgrant, the backend connections now log in using the service user credentials and then switch to the client user account using the newSET SESSION AUTHORIZATIONfeature in MariaDB 12. This makes it possible to use authentication plugins like ed25519 and PARSEC without having to configure anything extra in MaxScale. For more information, refer to the documentation of the use_service_credentials setting.Added support for the PARSEC authentication plugin. The plugin can be used with MariaDB 12 directly and with MariaDB 11.6 or later if the user mapping file is used. For more information, refer to the PARSEC authenticator documentation.
For more details, please refer to:
The changelog for the previous MaxScale version can be found here.
This page is licensed: CC BY-SA / Gnu FDL
Last updated
Was this helpful?

