Release Notes for MariaDB MaxScale 2.5.28

Notable Changes

• force_connection_keepalive parameter added, with default value false. (MXS-4720)

  • When force_connection_keepalive=false (the default), connection keepalive pings are sent only if the client is executing a query or has been idle for less than the duration configured in connection_keepalive

  • When force_connection_keepalive=true, keepalive pings are sent unconditionally to any backends that have been idle for longer than connection_keepalive seconds. This option can be used to emulate MaxScale's behavior prior to version 2.5.21 for cases where long-lived application connections rely on the old unconditional keepalive pings.

  • When force_connection_keepalive=true and connection_keepalive in MaxScale is set to a lower value than wait_timeout on the database, the timeouts controlled by wait_timeout will no longer be effective. In this circumstance, MaxScale unconditionally sends pings which make the client behave like it is not idle, so the connections will not be killed by wait_timeout.

• For MariaDB Monitor (mariadbmon), GRANT guidance has changed: (MXS-4672)

  • For complete instructions, see MariaDB Monitor.

  • For MariaDB Server 10.5.2 and above, it is recommended that CONNECTION ADMIN privilege be granted, since it allows the monitor to log in even if the server connection limit has been reached.

    GRANT CONNECTION ADMIN ON *.* TO 'maxscale'@'maxscalehost';
    

  • Certain privileges are required if performing cluster management operations. For MariaDB Server 11.0.1 and above, the SUPER privilege no longer conveys certain fine-grained privileges, so these must be granted directly.

    GRANT RELOAD, PROCESS, SHOW DATABASES, EVENT, SET USER, READ_ONLY ADMIN
      ON *.* TO 'maxscale'@'maxscalehost';
    GRANT REPLICATION SLAVE ADMIN, BINLOG ADMIN, CONNECTION ADMIN
      ON *.* TO 'maxscale'@'maxscalehost';
    GRANT SELECT ON mysql.user TO 'maxscale'@'maxscalehost';
    

    Privilege	Purpose
    BINLOG ADMIN	Delete binary logs (during reset-replication)
    CONNECTION ADMIN	Kill connections
    EVENT	List and modify server events
    PROCESS	Allows check whether the event_scheduler process is running
    READ_ONLY ADMIN	Allows read_only to be set
    RELOAD	Flush binary logs
    REPLICA MONITOR	View and manage replication connections
    REPLICATION SLAVE ADMIN	View and manage replication connections
    SELECT on mysql.user	View which users have SUPER
    SET USER	List and modify server events
    SHOW DATABASES	List and modify server events

  • If a separate replication user is defined (with replication_user and replication_password), REPLICATION SLAVE privilege is required.

    CREATE USER 'replication'@'replicationhost'
      IDENTIFIED BY 'replication-password';
    GRANT REPLICATION SLAVE ON *.* TO 'replication'@'replicationhost';
    

Issues Fixed

Supplemental Notes

• Enum values are case-sensitive. (MXS-4722)

  • For example, slave_selection_criteria=LEAST_CURRENT_OPERATIONS is correct while slave_selection_criteria=least_current_operations is not correct.

Platforms

In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 2.5.28 is provided for:

• CentOS 7 (x86_64)

• Debian 10 (x86_64, ARM64)

• Debian 11 (x86_64, ARM64)

• Debian 12 (x86_64, ARM64)

• Red Hat Enterprise Linux 7 (x86_64)

• Red Hat Enterprise Linux 8 (x86_64, ARM64)

• Red Hat Enterprise Linux 9 (x86_64, ARM64)

• Rocky Linux 8 (x86_64, ARM64)

• Rocky Linux 9 (x86_64, ARM64)

• SUSE Linux Enterprise Server 15 (x86_64, ARM64)

• Ubuntu 20.04 (x86_64, ARM64)

Installation

• Deploy Xpand Topology with MariaDB MaxScale 2.5

• Deploy Enterprise Cluster Topology with MariaDB MaxScale 2.5Deploy Enterprise Cluster Topology with MariaDB MaxScale 2.5

• Deploy Primary/Replica Topology with MariaDB MaxScale 2.5Deploy Primary/Replica Topology with MariaDB MaxScale 2.5

• Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 2.5Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 2.5

• Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 2.5Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 2.5

Upgrades

• Upgrade to MariaDB MaxScale 2.5