Release Notes for MariaDB MaxScale 6.1.1

NoSQL Listener

• MariaDB MaxScale's nosqlprotocol module supports a subset of MongoDB commands. This module transparently translates MongoDB commands to the equivalent SQL statements and executes queries on JSON data stored on a MariaDB backend. (MXS-2646)

• This feature is provided as a Technical Preview and should not be used for production workloads.

Ingest data from Apache Kafka (MXS-2588)

• MariaDB MaxScale's KafkaImporter module reads messages from Apache Kafka and streams JSON to a MariaDB backend.

Connect and query from MaxScale's web GUI (MXS-3257)

• MariaDB MaxScale's MaxGUI integrates a visual client. The visual client allows you to connect to and query a MariaDB backend.

Automatically sync MaxScale configuration data

• MariaDB MaxScale's config_sync_cluster parameter enables synchronization of configuration changes between MaxScale instances through a MaxScale-monitored database. (MXS-2808)

• Prior to this feature, configuration sync was performed outside MaxScale, either manually or with custom automation.

Pipelined execution of write statements by Read-Write Split Router

• The readwritesplit router supports pipelined execution of write statements. No action is needed to enable this feature. (MXS-1245)

PAM Authenticator user mapping

• The pam_backend_mapping parameter of the PAMAuth authenticator enables mapping of users to normal MariaDB accounts. (MXS-3475)

Automated failover for KafkaCDC and Avrorouter

• The cooperative_replication parameter of the kafkacdc router enables high availability through automated failover between multiple MaxScale instances. (MXS-1687)

• The cooperative_replication parameter of the avrorouter router enables high availability through automated failover between multiple MaxScale instances. (MXS-1687)

Read Connection Router read restriction

• The master_accept_reads parameter has been added to the readconnroute router. (MXS-3091)

• By default, master_accept_reads=true

• When master_accept_reads=false, readconnroute will not route reads to the current Primary (master) server.

Replication lag triggered script execution

• The script_max_replication_lag parameter of the mariadbmon monitor triggers the execution of a defined script when replication lag exceeds a defined threshold. (MXS-2723)

Enforce writable Primary (master)

• A Primary (master) should never become read-only during normal operations, but it could become read-only in certain problematic circumstances. For example:

  • The Primary could become read-only if the database administrator accidentally set read_only to ON on the server.

  • The Primary could remain read-only if mariadbmon promoted the node to Primary during a switchover or failover, but MaxScale crashed before mariadbmon could set read_only to OFF on the new Primary.

• To configure the behavior of mariadbmon when it detects that the Primary has become read-only, the enforce_writable_master parameter has been added to the mariadbmon monitor:

  • When the enforce_writable_master parameter is set to true, mariadbmon will remove the read-only state from the Primary. The Primary will temporarily be unavailable for writes while mariadbmon corrects the state of the node. (MXS-3268)

  • When the enforce_writable_master parameter is set to false, mariadbmon will failover to a new Primary.

• Prior to this release, mariadbmon would always failover to a new Primary.

maxctrl accepts configuration defaults

• When ~/.maxctrl.cnf exists, maxctrl will use values from the [maxctrl] section as command-line argument defaults. (MXS-3482)

MaxScale logs via REST API

• The MaxScale REST API enables access to MaxScale log data through HTTP calls or a WebSocket stream.

Runtime filter changes

• Logging options for filters can be changed at runtime with maxctrl alter filter (MXS-3108)

• The filters of a session can be changed with maxctrl alter session-filters (MXS-3108)

• Session changes can be made with maxctrl or REST API.

Individual listeners can be stopped

• MaxCtrl supports stopping individual listeners. (MXS-3108)

• maxctrl stop listener will stop a listener.

• Adding the --force option to a stop command forces all open connections to be closed when the associated object is stopped.

Session command history limit

• readwritesplit router supports the max_sescmd_history parameter to limit the session command history.

• readwritesplit router statistics now include avg_sescmd_history_length and max_sescmd_history_length to aid in tuning max_sescmd_history (MXS-2748)

View Logs from MaxGUI

• MariaDB MaxScale's MaxGUI integrates log viewing, accessible using the "MaxScale Logs" tab. (MXS-3154)

TLS parameters for listeners and servers can be modified at runtime (MXS-3128)

• TLS parameters for listeners can be modified using maxctrl alter listener, the REST API, or MaxGUI.

• TLS parameters for servers can be modified using maxctrl alter server, the REST API, or MaxGUI.

• Prior to this release, TLS parameters for listeners and servers were modifiable only when the object was created.

ssl=true replaces ssl=required

ssl=false replaces ssl=disabled

TLS and Authentication for Kafka

• The kafakacdc module includes kafka_ssl_* and kafka_sasl_* parameters to enable TLS and authentication for Kafka. (MXS-3411)

• The kafkaimporter module includes kafka_ssl_* and kafka_sasl_* parameters to enable TLS and authentication for Kafka. (MXS-3411)

With the readwritesplit router, causal_reads support binary protocol Prepared Statements. (MXS-3499)

Prepared Statement caching

• With the readwritesplit router, the reuse_prepared_statements parameter enables reuse of identical binary protocol Prepared Statements inside the same client connection. (MXS-2351)

With the hintfilter filter, routing hints are supported in binary protocol Prepared Statements. (MXS-2838)

dbfwfilter is deprecated (but not removed) in MaxScale 6. An alternative solution will be provided with MaxScale 7.

Multi-line configuration parameters are deprecated (but not removed) in MaxScale 6. Multi-line configuration parameters will be removed with MaxScale 7.

The default value of threads has changed from 1 to auto (MXS-3537)

Deploy Xpand Topology with MariaDB MaxScale 6

Deploy Enterprise Cluster Topology with MariaDB MaxScale 6Deploy Enterprise Cluster Topology with MariaDB MaxScale 6

Deploy Primary/Replica Topology with MariaDB MaxScale 6Deploy Primary/Replica Topology with MariaDB MaxScale 6

Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 6Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 6

Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 6Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 6

Upgrade to MariaDB MaxScale 6