MaxScale 23.02 Changelog

• A transition from the traditional master/slave terminology to the primary/replica terminology has been started. In the documentation and in the logging the transition has been made, but in configuration settings and command output the traditional terminology is still used. Conceptually, master/slave and primary/replica are completely interchangeable.

• MariaDB Monitor now preserves the MASTER_USE_GTID-setting of a replica when redirecting one during switchover and failover. When starting a new replication connection on a previous replica, Slave_Pos is used. When starting a new replication connection on a previous primary, Current_Pos is used.

• Added replication_custom_options-setting to both MariaDB Monitor and server. This setting enables e.g. setting SSL certificates for replication connections. See MariaDB Monitor documentation for more information.

• Create-Backup and Restore-From-Backup commands added to MariaDBMonitor.

• The csmon and auroramon monitors that were deprecated in 22.08.2 have been removed.

• The obsolete maxctrl drain command has been removed. Use maxctrl set server <name> drain to use the built-in draining mechanism.

• The maxctrl cluster commands have been removed. Use the built-in configuration synchronization to synchronize the configurations of multiple MaxScale instances.

• The REST-API is now supports ODBC-type connections in the /sql endpoints. For more information, refer to the SQL resource documentation.

• The REST-API query endpoint now supports asynchronous query execution using the async=true option.

• The new /sql/:id/etl endpoints allow ETL operations to be done from ODBC data sources into MariaDB servers. For more information on the new API functions, refer to the SQL resource documentation.

• The number of routing threads MaxScale uses can now be changed at runtime.

• The Audit-Log allows all REST-API calls to be logged.

• MaxScale now supports Xpand parallel replication streams that go through MaxScale.

• Authentication can now be enabled when Redis is used as the cache storage.

• SSL/TLS can now be used in the communication between MaxScale and Redis when Redis is used as the storage for the cache.

• Some Cache configuration parameters, most notable the rules, can now be changed at runtime.

• Support for inbound proxy protocol added.

• Ed25519Auth-plugin added. The plugin enables authentication with the MariaDB Server ed25519 authentication plugin.

• MaxGUI Query Editor has been renamed to "Workspace," and its internal storage key has been modified. As a result, the query history, snippets, and user preferences settings are restored to their default values.

• The redundant options for create server and create listener that were deprecated in 22.08 have been removed in MaxScale 23.02. The use of explicit options has been superseded by the use of key=value parameters in allcreate commands.

For more details, please refer to:

• MariaDB MaxScale 23.02.15 Release Notes

• MariaDB MaxScale 23.02.14 Release Notes

• MariaDB MaxScale 23.02.13 Release Notes

• MariaDB MaxScale 23.02.12 Release Notes

• MariaDB MaxScale 23.02.11 Release Notes

• MariaDB MaxScale 23.02.10 Release Notes

• MariaDB MaxScale 23.02.9 Release Notes

• MariaDB MaxScale 23.02.8 Release Notes

• MariaDB MaxScale 23.02.7 Release Notes

• MariaDB MaxScale 23.02.6 Release Notes

• MariaDB MaxScale 23.02.5 Release Notes

• MariaDB MaxScale 23.02.4 Release Notes

• MariaDB MaxScale 23.02.3 Release Notes

• MariaDB MaxScale 23.02.2 Release Notes

• MariaDB MaxScale 23.02.1 Release Notes

• MariaDB MaxScale 23.02.0 Release Notes

The changelog for the previous MaxScale version can be found here.