All pages
Powered by GitBook
1 of 35

MariaDB MaxScale 21.06 Release Notes

Review the official release notes for MariaDB MaxScale 21.06. This section details new features like the Kafka CDC router and causal reads, as well as all bug fixes and functional changes. Sources

MariaDB MaxScale 21.06.20 Release Notes

Release 21.06.20 is a GA release.

This document describes the changes in release 21.06.20, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-5618 Maxctrl interactive mode doesn't use --tls-verify-server-cert=false

  • MXS-5608 optimistic_trx causes a query to hang

  • MXS-5599 Processing of conditional headers is incorrect

  • MXS-5598 MaxCtrl fails to read large inputs from stdin

  • MXS-5590 REST-API always sends a Connection: close header

  • MXS-5582 Add a Service with a CLUSTER as its target breaks CONFIG SYNC

  • MXS-5577 Aborted connection on backend mariadb with persistpool maxscale

  • MXS-5576 Maxctrl config permission check error message is misleading

  • MXS-5567 Wrong password in interactive mode is only seen after the first command

  • MXS-5566 --secretsdir has no default value

  • MXS-5563 Using PKCS#1 private key in the REST-API results in cryptic errors

  • MXS-5556 Trailing parts of large session command are not routed correctly

  • MXS-5542 kafkacdc commits offsets when it probes GTIDs from Kafka

  • MXS-5541 Logs Archive page doesn't show useful API error

  • MXS-5525 Masking with functions uses wrong rule settings

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

MariaDB MaxScale 21.06.16 Release Notes -- 2024-06-03

NOTE MaxScale 6.4 was renamed to 21.06 in May 2024. Thus, what would have been released as 6.4.16 in June, was released as 21.06.16. The purpose of this change is to make the versioning scheme used by all MaxScale series identical. 21.06 denotes the year and month when the first 6 release was made.

Release 21.06.16 is a GA release.

This document describes the changes in release 21.06.16, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-5067 Add "enforce_read_only_servers" feature to MariaDB Monitor

Bug fixes

  • MXS-5095 Master Stickiness state is not documented

  • MXS-5090 ability to setup .secrets file location

  • MXS-5085 max_slave_connections=0 may create slave connections after a switchover

  • MXS-5083 ssl_version in MaxScale and tls_version in MariaDB behave differently

  • MXS-5082 Password encryption format change in 2.5 is not documented very well

  • MXS-5081 The values of ssl_version in MaxScale and tls_version in MariaDB accept different values

  • MXS-5074 Warning about missing slashes around regular expressions is confusing

  • MXS-5048 Problem in hostname matching when using regex (%) for user authentication

  • MXS-5039 cooperative_monitoring_locks can leave stale locks on a server if network breaks

  • MXS-5038 Maxscale key limitations

  • MXS-5031 enforce_read_only_slaves can set master to read_only

  • MXS-5021 gdb-stacktrace is incorrectly presented as a debug option

  • MXS-5014 During Failover Passive MaxScale route writes to the Old Master

  • MXS-5010 Session commands that are executed early are not validated

  • MXS-5009 --basedir is broken

  • MXS-4902 MariaDB Monitor command reset-replication can be started on a secondary MaxScale

  • MXS-4834 MaxScale should log a warning if failover may lose transactions

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 21.06.17 Release Notes -- 2024-09-09

Release 21.06.17 is a GA release.

This document describes the changes in release 21.06.17, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-5232 Large batches of session commands may leave sessions alive for a long time

  • MXS-5227 MaxScale does not drop supplementary groups if --user is used

  • MXS-5226 LICENSE.TXT is a dangling symlink in RPMs

  • MXS-5213 Erroneous "Cluster gtid domain is unknown" error message during failover

  • MXS-5209 Reads with max_slave_connections=0 after a switchover do not discard stale connections

  • MXS-5200 CMake 3.28.3 warnings

  • MXS-5198 Default logrotate config in .deb / docu missing params

  • MXS-5196 /maxscale/logs/data may return no data if maxlog=0 and syslog=1

  • MXS-5193 Multi-statement commands may end up being stored in the session command history

  • MXS-5191 Two cache filters in same service causes errors on session creation

  • MXS-5171 MaxScale does not have time to open the file during rotation for a new binlog

  • MXS-5162 Post reboot binlog router entered stuck state

  • MXS-5160 postinst script prints output while installing

  • MXS-5146 23.08.6 build ppc64le fails

  • MXS-5133 Memory leak in namedserverfilter

  • MXS-5131 comment filter uses the wrong module name

  • MXS-5127 DEALLOCATE PREPARE is not routed to all nodes

  • MXS-5121 MaxScale detects wrong server character set

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 21.06.18 Release Notes -- 2024-12-09

Release 21.06.18 is a GA release.

This document describes the changes in release 21.06.18, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

  • CVE-2023-0437 Fixed by MXS-5400 Upgrade MongoC library to 1.27.5

  • CVE-2024-7553 Fixed by MXS-5400 Upgrade MongoC library to 1.27.5

Bug fixes

  • MXS-5394 Empty passwords are shown as non-empty if password encryption is enabled

  • MXS-5387 Crash in MariaDBParser::Helper::get_query_info()

  • MXS-5378 Nested listener parameters depend on protocol being defined

  • MXS-5377 Debug assert if backend fails during multi-packet query

  • MXS-5374 Kafkaimporter doesn't work with MariaDB 11

  • MXS-5372 timeout in kafkacdc is not a duration type

  • MXS-5363 GDB stacktraces may hang

  • MXS-5357 Improve MariaDB Monitor documentation on auto_failover and auto_rejoin

  • MXS-5344 Kafkaimporter constraint makes it difficult to use with kafkacdc

  • MXS-5343 Kafkacdc does not mention row-based replication as a requirement

  • MXS-5341 User account manager hangs on shutdown

  • MXS-5339 Slow servers may cause OOM situations if prepared statements are used

  • MXS-5302 Prepared statements should never be removed from session command history

  • MXS-5298 Kafkacdc always reads last GTID from Kafka on startup

  • MXS-5295 SET NAMES UTF8MB4,autocommit=0 is not detected correctly

  • MXS-5273 The --config-check fails if /var/cache/maxscale cannot be read

  • MXS-5268 Read-only error during read-write transaction should trigger transaction replay

  • MXS-5264 MaxScale installs scripts with non-standard file permissions

  • MXS-5263 Valgrind reports read from uninitialized GWBUF for ccrfilter

  • MXS-5259 Retrying of reads on the current primary unnecessarily requires delayed_retry

  • MXS-5258 delayed_retry should not retry interrupted writes

  • MXS-5256 SET statements multiple values are not parsed correctly

  • MXS-5255 test_mxb_string sometimes times out on aarch64

  • MXS-5248 Debug assertion due to non-existent dcall ID

  • MXS-5247 Remove obsolete prelink script

  • MXS-5245 MaxCtrl does not accept dot notation for nested parameters

  • MXS-5239 Listener with ssl=false allows user accounts created with REQUIRE SSL to log in

  • MXS-5236 wsrep_desync behavior is undocumented

  • MXS-5234 webpack warns about yargs

  • MXS-5229 Master Stickiness status not displayed correctly with use_priority

  • MXS-5178 Replicas after maxscale binlog don't get updates

Known Issues and Limitations

In the previous version of MaxScale, maxctrl was implemented as a JavaScript script that was run using the node interpreter on the platform. That introduced a dependency on node that earlier was not present. In this version of MaxScale, maxctrl is again a native executable without that dependency.

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 21.06.19 Release Notes

Release 21.06.19 is a GA release.

This document describes the changes in release 21.06.19, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

  • CVE-2024-21538 Fixed by MXS-5478 Container Image vulnerability CVE-2024-21538 (MXS)

Bug fixes

  • MXS-5536 Early mismatched responses to session commands do not close connections

  • MXS-5529 Session commands with max_slave_connections=0 after switchover do not discard stale connections

  • MXS-5527 The "INSERT INTO...RETURNING" syntax breaks causal_reads

  • MXS-5519 Documentation regarding mixing of cooperative_monitoring_locks and passive is unclear

  • MXS-5508 Relationship selections auto-cleared when creating a new monitor object

  • MXS-5507 readwritesplit enables multi-statements regardless of the state of causal_reads

  • MXS-5492 idle_session_pool_time=0s does not fairly share connections

  • MXS-5488 Need Documentation updates for Maxscale install recommendation

  • MXS-5466 MaxCtrl warnings are very verbose

  • MXS-5455 Errors during loading of users lack the service name

  • MXS-5450 maxctrl list queries fails

  • MXS-5449 Encrypted passwords cannot be used with maxctrl

  • MXS-5443 Log message: Unknown prepared statement handler given to MaxScale

  • MXS-5439 Backend connections with fail with EAGAIN

  • MXS-5437 Failed authentication warnings do not mention lack of client-side SSL as the reason of the failure

  • MXS-5432 MaxScale 24.02.04 not closing DB Connections properly

  • MXS-5419 Duration types that only take seconds return ms as units instead of s

  • MXS-5415 retry_failed_reads is not affected by delayed_retry_timeout

  • MXS-5403 Debug assertion on very large binary protocol prepared statements

  • MXS-5398 Some log messages are not logged when session_trace is used

  • MXS-5397 NVL and NVL2 are not detected as builtin functions outside of sql_mode=ORACLE

  • MXS-5395 Kafkacdc errors for wrong GTID positions are not clear

  • MXS-5382 Errors due to max_connections being exceeded are always fatal 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 document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.0.0 Release Notes -- 2021-06-30

The versioning scheme has changed; the major number will be increased at the yearly major release, the minor number will be increased at intermediate scheduled releases and the patch number whenever a maintenance release is made. Each major release is separately maintained.

According to the old scheme, this MaxScale release would have been called 2.6 and the version number would have been 2.6.0.

Release 6.0.0 is a Beta release.

This document describes the changes in release 6, when compared to release 2.5.

For any problems you encounter, please consider submitting a bug report on our Jira.

Changed Features

MXS-3107 Columnstore monitor

The Columnstore monitor that in this release only supports Columnstore version 1.5, is now capable of adjusting itself automatically to any changes in the cluster. In the configuration it is only specified a node using which the monitor get in contact with the cluster, but after that the monitor autonomously figures out the cluster configuration and automatically adapts to any changes in the configuration. For more details, please consult themonitor documentation.

MXS-3499 causal_reads and Prepared Statements

The causal_reads feature now supports binary protocol prepared statements. For more information, refer to thedocumentation for causal_reads.

MXS-2838 Hintfilter and Prepared Statements

The hintfilter now supports routing hints in binary protocol prepared statements. For more information, refer to the hintfilterdocumentation.

MXS-3219 Galera Server States

The servers monitored by a galeramon will now also display extra status information in the REST API output regarding the server state. MaxCtrl will automatically combine this for the output of maxctrl list servers.

MXS-1245 Readwritesplit Statement Pipelining

Readwritesplit now supports "pipelined" execution of write statements. This significantly improves the performance of batch data loading with connectors that use it (e.g. the MariaDB JDBC and Node.JS connectors).

MXS-3128 Runtime Alteration of TLS Parameters

The TLS parameters for listeners and servers can now be modified at runtime. Previously the parameters were only modifiable when the object was being created.

MXS-3537 Default Value of threads

The default value of threads was changed from 1 to auto.

Dropped Features

ssl=required and ssl=disabled

The required and disabled values for the ssl parameter have been removed. Replace them with ssl=true and ssl=false.

Deprecated Features

Database Firewall filter

The filter is deprecated in MaxScale 6 and will be removed in MaxScale 22.08.

Multi-line Configuration Parameters

The ability to define a single configuration parameteron multiple lines is deprecated and will be removed in MaxScale 22.08.

New Features

MXS-2646 nosqlprotocol protocol module

This module implements a subset of the MongoDB® wire protocol and transparently converts MongoDB commands into the equivalent SQL statements that subsequently are executed on a MariaDB server. This allows client applications utilizing some MongoDB client library to use a MariaDB server as backend. As the conversion is performed in the protocol module, this functionality can be used together with all MaxScale routers and filters. Please see the nosqlprotocoldocumentation for more information.

MXS-3482 Defaults can be specified for maxctrl

If the file ~/.maxctrl.cnf exists, maxctrl will use any values in the section[maxctrl] as defaults for command line arguments. Please see the maxctrldocumentation for details.

MXS-3411 TLS and Authentication for Kafka

The KafkaCDC as well as the new KafkaImporter both new support TLS and basic SASL authentication for Kafka.

For more information, refer to the KafkaCDC and KafkaImporter documentation.

MXS-3178 REST API Log Interface

The REST API is now able to deliver the MaxScale logs both as a normal HTTP resource as well as WebSocket stream. For more information, refer to the REST API documentation.

MXS-3108 Session Alteration

The logging options for filters can be changed at runtime with maxctrl alter filter and the filters of a session can be modified with maxctrl alter session-filters. For more information, refer to the MaxCtrldocumentation as well as the REST APIdocumentation.

MXS-2806 Stopping of Individual Listeners

Individual listeners can now be stopped with the maxctrl stop listener command. The new --force option added to the stop commands can be used to force all open connections to be closed when the associated object is stopped.

MXS-2808 Configuration Synchronization

A new configuration synchronization feature has been added to MaxScale. This feature allows multiple MaxScale instances to share a configuration file that is synchronized via the database cluster monitored by MaxScale. For more information, refer to the config_sync_clusterdocumentation.

MXS-2588 Data Ingestion From Kafka

The KafkaImporter module can be used to import JSON data from Kafka into MariaDB. For more information, refer to the KafkaImporterdocumentation.

MXS-2351 Prepared Statement Caching

Readwritesplit is now capable of caching prepared statements for individual sessions. For more information, refer to thedocumentation for thereuse_prepared_statements parameter.

MXS-1687 KafkaCDC and Avrorouter Failover

The KafkaCDC and Avrorouter modules now support automated failover of the replication stream when configured to replicate from servers or from a cluster. For more information, refer to theKafkaCDC andAvrorouter documentation.

MXS-2748 Session command history to RWS

Readwritesplit statistics now has two new entries:avg_sescmd_history_length and max_sescmd_history_length. These are helpful when tuning max_sescmd_history to avoid session command history to be too short, leading to potential inconsistencies, or to become too large, leading to wasted memory.

MXS-3091 Restrict RCR reads to slaves

Readconnroute has a new option master_accept_reads similar to the one in Readwritesplit. When master_accept_reads=false RCR will not route reads to the current master.

MXS-3257 SQL queries tool

A graphical user interface tool to write, run SQL queries and visualize the results. For more information, refer to the MAXGUI documentation.

MXS-3154 Logs viewer

A graphical user interface for reading and filtering MaxScale's log. For more information, refer to the MAXGUI documentation.

MariaDB-Monitor

MXS-2723 Can launch monitor script when slave server exceeds replication lag limit. See documentation for more information.

MXS-3268 Can disable read_only on master if it's set. Seedocumentation for more information.

MXS-3475 PAM user mapping

PAM-Authenticator supports mapping incoming PAM users to MariaDB users. Seedocumentation for more information.

Bug fixes

  • MXS-3592 MaxCtrl object creation doesn't convert values to JSON

  • MXS-3537 Default value of threads is not optimal

  • MXS-3515 COM_STMT_EXECUTE with ID -1 isn't handled correctly

  • MXS-3443 Query performance degradation in 2.5

  • MXS-3184 COM_STMT_EXECUTE with FOUND_ROWS not routed to previous target

  • MXS-3028 Node wrongly in Maintenance, Running when the node is actually Down

  • MXS-2915 TLS version not used by mxq::MariaDB

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.1.0 Release Notes -- 2021-07-15

Release 6.1.0 is a GA release.

This document describes the changes in release 6.1.0, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3661 The list of servers might get duplicated for routers using mariadbmon

  • MXS-3660 MaxScale crashes if backend connection creation fails on a system error

  • MXS-3658 If the monitor is dynamic, both static and volatile servers will be used.

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.1.1 Release Notes

Release 6.1.1 is a GA release.

This document describes the changes in release 6.1.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3697 MaxCtrl config file check fails when executed from the root directory

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.1.2 Release Notes -- 2021-09-27

Release 6.1.2 is a GA release.

This document describes the changes in release 6.1.2, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3775 Hang in RoutingWorker::execute_concurrently

  • MXS-3774 Maxscale crash during xpand scale up

  • MXS-3773 nosqlprotocol should report 0 as the minimum wire protocol version

  • MXS-3767 connector_plugindir does not pick up the default location.

  • MXS-3766 Not able to insert data on Masking enabled table

  • MXS-3759 Client hangs forever when server failed or restarted

  • MXS-3757 Don't allow any SIMD code run until called

  • MXS-3754 maxscale-6.1.1-1.rhel.8.x86_64 crashes and coredumps on first startup after upgrade maxscale-2.5.15-1.rhel.8.x86_64

  • MXS-3750 6.1.1 CentOS7 x86_64 RPMs fail on older CPUs without avx2 extension

  • MXS-3704 MaxScale always advertises the SESSION_TRACK capability even with servers that don't support it (XPand)

  • MXS-3580 Avrorouter should store full GTID coordinates

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.1.3 Release Notes -- 2021.10.01

Release 6.1.3 is a GA release.

This document describes the changes in release 6.1.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3796 maxscale 6.1.2 killed by SystemD watchdog

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.1.4 Release Notes -- 2021-10-18

Release 6.1.4 is a GA release.

This document describes the changes in release 6.1.4, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3817 The location of the GUI web directory isn't documented

  • MXS-3816 Queries are not always counted as reads with router_options=slave

  • MXS-3812 Hints for prepared statements can be lost if a query fails

  • MXS-3804 Result size accounting is wrong

  • MXS-3803 Debug assertion in readwritesplit

  • MXS-3801 Unexpected internal state with read-only cursor and result with one row

  • MXS-3799 Destroyed monitors are not deleted

  • MXS-3798 Race condition in service destruction

  • MXS-3791 Fix generix multistatement bug

  • MXS-3790 Fix luafilter

  • MXS-3788 Debug assertion with default config and transaction_replay=true

  • MXS-3779 binlogrouter logs warnings for ignored SQL

  • MXS-3768 Query Editor requires admin privileges

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.2.0 Release Notes -- 2021-11-26

Release 6.2.0 is a GA release.

This document describes the changes in release 6.2.0, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-3813 Support PS direct execution in hintfilter

  • MXS-3771 Add row count to qlafilter

  • MXS-3755 Handle multiple replication sources on rejoin

  • MXS-3733 Add keytab filepath configuration option to GSSAPI authenticator

  • MXS-3701 Add canonical query form into qlafilter

  • MXS-3681 Refactor SQL GUI to support multiple SQL connections

  • MXS-3680 Multiple SQL connections

  • MXS-3675 History/favorite queries

  • MXS-3659 Show Slave Status in GUI

  • MXS-3645 Transaction Performance Monitoring Filter functionality moved to Qlafilter

  • MXS-3639 Show Stored procedures and Triggers in schema tree

  • MXS-3638 Multi-tab query editor

  • MXS-3636 Filter result by specific column

  • MXS-3635 Quicker access to "Place Schema in Editor"

  • MXS-3634 Add DDL editor

  • MXS-3632 Add right click context menu to schema tree

  • MXS-3613 Support PS with metadata skip (i.e. MARIADB_CLIENT_CACHE_METADATA)

  • MXS-3526 GSSAPI authenticator supports only one principal and only the default location for the keytab

  • MXS-3475 Extend PAM support to include Group Mapping

  • MXS-3453 Add counter for failed authentication attempts

  • MXS-3363 Make tee filter also syncronously

  • MXS-3281 r/w split slave_selection_criteria should have none

  • MXS-3037 show detail processlist like at mariadb

  • MXS-2074 Handle prepared statements in NamedServerFilter

  • MXS-1892 Support deprecate eof

Bug fixes

  • MXS-3883 nosqlprotocol parameters are not serialized correctly

  • MXS-3881 Maxscale killing connection to backend node when load data infile is run with transaction replay

  • MXS-3880 Bias value for open connections is too large

  • MXS-3878 The create server command doesn't allow custom parameters

  • MXS-3876 sys schema not ignored by schemarouter

  • MXS-3857 Pinloki initial gtid scan incorrectly reads entire files

  • MXS-3849 Unable to configure nested parameters via MaxCtrl

  • MXS-3847 Node hostname is not escaped properly

  • MXS-3846 debug=enable-statement-logging doesn't work with mxq::MariaDB

  • MXS-3845 Sending binlog events is inefficient

  • MXS-3838 Add reconnect functionality to the GUI

  • MXS-3836 refresh_databases does nothing

  • MXS-3835 Timeout for connection dialog in the GUI is not parsed as number

  • MXS-3834 SQL API has no reconnect functionality

  • MXS-3833 Query editor timeout is too aggressive

  • MXS-3824 Allow symbolic link for path to directory /usr/share/maxscale/gui

  • MXS-3815 maxscale crash

  • MXS-3814 maxscale rpl_state is empty

  • MXS-3809 When MariaDBMonitor acquires lock majority, the log message gives the impression that auto_failover is enabled even when it is not configured

  • MXS-3800 Not enough information in server state change messages

  • MXS-3793 Race condition in GCUpdater shutdown

  • MXS-3778 MaxScale crashes when using Cache filter

  • MXS-3777 COMMIT in prepared statement causes warnings

  • MXS-3772 Qlafilter message timing is inconsistent

  • MXS-3770 Bundle Connector-C plugins with MaxScale

  • MXS-3736 Crash with kafkaimporter and no servers

  • MXS-3730 idle_session_pool_time=0s doesn't immediately pool idle connections

  • MXS-3720 idle_session_pool_time should support prepared statements

  • MXS-3717 Crash on object type change with config_sync_cluster

  • MXS-3711 Qlafilter cannot be modified at runtime

  • MXS-3710 Namedserverfilter cannot be modified at runtime

  • MXS-3709 Masking filter cannot be modified at runtime

  • MXS-3690 MaxCtrl parameter format is inconsistent

  • MXS-3689 Protocol module configurations are not persisted

  • MXS-3688 MaxCtrl doesn't support listener module parameters

  • MXS-3687 Lack of nested parameters is not detected

  • MXS-3686 Object names with characters outside of the ASCII range are not rejected

  • MXS-3685 nosqlprotocol doesn't start TLS session

  • MXS-3672 MaxCtrl output is not very readable

  • MXS-3630 Update user accounts when backend login fails

  • MXS-3618 config_sync_cluster change detection is inadequate

  • MXS-3594 Filters can be altered but no filter declares parameters as alterable

  • MXS-3580 Avrorouter should store full GTID coordinates

  • MXS-3514 Speed up special query parsing (pcre2)

  • MXS-3498 Improve Multistatement detect performance

  • MXS-3458 Execution of PS fails when strict_sp_calls is enabled

  • MXS-3359 QLA filter append= should default to true, at least when using log_type=unified

  • MXS-3353 Tee filter loses statements if branch target is slower

  • MXS-3308 Passing options in interactive mode returns an empty error

  • MXS-2992 ALTER TABLE statements not working with masking filter

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.2.1 Release Notes -- 2022-01-13

Release 6.2.1 is a GA release.

This document describes the changes in release 6.2.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-3894 Invent a configuration option to allow transaction replay ignore checksum check

  • MXS-3379 Make transaction_replay less strict

  • MXS-2353 Per service log_info

Bug fixes

  • MXS-3943 Altering xpandmon at runtime fails

  • MXS-3941 create_one_connection_for_sescmd() doesn't correctly replace m_current_master

  • MXS-3940 Debug assertion in mariadb_backend.cc

  • MXS-3939 Debug assertion during transaction replay

  • MXS-3938 Debug assert in xpandmon

  • MXS-3937 Transaction replay time limits are unpredictable

  • MXS-3934 Linking a service at runtime to an xpandmon doesn't work

  • MXS-3929 connection stalled after executing a stored procedure with OUT parameter

  • MXS-3928 MaxScale logs a warning when users are loaded from a Xpand cluster

  • MXS-3927 Some log messages do not contain the session ID

  • MXS-3924 Session commands are not retried with delayed_retry

  • MXS-3920 Can't connect to MaxScale when schema uses utf8mb4 chars >= U0080

  • MXS-3917 Crash during set server maintenance --force

  • MXS-3915 Autocommit tracking doesn't work correctly

  • MXS-3911 Monitor parameters table is not modifiable (GUI)

  • MXS-3909 Skip http_proxy when address is localhost

  • MXS-3908 MaxScale crashes (double free or corruption)

  • MXS-3907 Unexpected result state

  • MXS-3900 Add multi-threaded stack traces

  • MXS-3897 MaxScale crashes when executing CDC process to kafka

  • MXS-3896 When reading password from stdin via redirect, interactive use is no longer possible

  • MXS-3893 read/write split service incorrectly times out valid sessions on master if timeout happens on replica

  • MXS-3841 LIMIT should be added for each select query automatically

  • MXS-3807 Using the binlog router as the source for KafkaCDC router is unreliable

  • MXS-3544 Use virtual scroll on maxscale log view to fix memory issue

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.2.2 Release Notes -- 2022-02-14

Release 6.2.2 is a GA release.

This document describes the changes in release 6.2.2, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-3989 Rebalancing may cause MaxScale to crash

  • MXS-3978 Binlog router appends -BinlogRouter to master version string again and again ...

  • MXS-3973 Session capabilities are not frozen on session startup

  • MXS-3966 MariaDBMonitor does not log connection error on startup

  • MXS-3959 Transaction replay doesn't reset transaction on implicit commit

  • MXS-3958 MaxScale stalls and crashes occasionally

  • MXS-3955 Crash after unexpected result

  • MXS-3953 Transaction start written to binlog prematurely

  • MXS-3949 "transaction" is always parsed as a reserved word

  • MXS-3948 Toggle query result columns isn't working as expected

  • MXS-3932 Xpand monitor doesn't show full configuration in diagnostic output

  • MXS-3886 Hang in RoutingWorker::execute_concurrently semaphore.hh:146

  • MXS-3865 Shutdown bug

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.2.3 Release Notes -- 2022-03-09

Release 6.2.3 is a GA release.

This document describes the changes in release 6.2.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4038 maxctrl reload service does not bypass the users refresh rate limit

  • MXS-4035 Cache warns too aggressively of statements that cannot be cached.

  • MXS-4030 Query Editor: Y axis dropdown doesn't show accurate table columns

  • MXS-4021 Monitor is not shown in MaxGUI's dashboard if the monitor is stopped

  • MXS-4011 maxscale.cnf.template on MaxScale 6.x refers to 2.5 documentation

  • MXS-4008 Query classifier cache does not properly record all used memory

  • MXS-4007 Active operation count is wrong after failed causal read

  • MXS-4005 Crash on server failure with causal_reads=local

  • MXS-4004 Race condition in KILL command execution

  • MXS-4002 KILL commands leave no trace in the log

  • MXS-4001 The Cache filter cannot cope with the Redis server closing the connection

  • MXS-4000 Binlogrouter creates malformed replication events

  • MXS-3988 Document implications of changed auth_all_servers default on schemarouter

  • MXS-3984 COM_CHANGE_USER from 'user' to 'user' succeeded on MaxScale yet failed on backends

  • MXS-3979 Not all state transitions are written to the log

  • MXS-3957 Remove the Don't Limit option for max_rows value of the Query Editor

  • MXS-3954 Got below signal 11 error after upgrading maxscale version maxscale 6.2.1

  • MXS-3945 Sync marker mismatch while reading Avro file

  • MXS-3931 Check certificates with extendedKeyUsage options set for correct purpose flags

  • MXS-3808 Improve Rest API performance

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.2.4 Release Notes -- 2022-03-30

Release 6.2.4 is a GA release.

This document describes the changes in release 6.2.4, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-3997 Name threads for better CPU usage view

  • MXS-3665 Provide more feedback on TLS cipher mismatch

Bug fixes

  • MXS-4061 Query Editor: Query history isn't cleared after passing the retention period

  • MXS-4058 Query Editor: Connection to [::]:9999 failed. Error 2002: Can't connect to server on '::' (113)

  • MXS-4053 The cache does not handle multi-statements properly.

  • MXS-4045 Add maxctrl command for dumping the whole REST API output

  • MXS-4043 Creating a listener in the GUI requires defining the service twice

  • MXS-4040 Mariadbmon constantly logs errors if event scheduler is disabled

  • MXS-4018 Query Editor: Column names should be auto adjust in the Data Preview

  • MXS-3936 Expected status message in the context of queued command, but received a ARRAY

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.3.0 Release Notes -- 2022-04-14

Release 6.3.0 is a GA release.

This document describes the changes in release 6.3.0, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-3968 Add support for SSL

  • MXS-3925 Implement authentication

  • MXS-3902 Limit total number of connections to backend

  • MXS-3844 Cooperative Monitor Indicator

  • MXS-3806 Provide filtering for the KafkaCDC Router

  • MXS-3413 The persistence of on-the-fly parameter changes needs to be somehow exposed, and more manageable.

Bug fixes

  • MXS-4082 SQL endpoint doesn't show errors for resultsets

  • MXS-4080 Query Cache detects wrong parse error in INSERT or DELETE

  • MXS-4078 maxctrl commands exception with file .maxctrl.cnf

  • MXS-4074 Status of boostrap servers not always the same as the status of corresponding runtime servers

  • MXS-4071 A horizontal scrollbar appears in some dialogs

  • MXS-4064 Address field truncated in GUI

  • MXS-4053 The cache does not handle multi-statements properly.

  • MXS-4027 Query Editor Chart is Not Hiding Or need close button For the Chart

  • MXS-3977 The servers table in monitor details page shouldn't be sorted by default

  • MXS-3962 Automatically generated dynamic config contains default values for unmodified params

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.3.1 Release Notes -- 2022-05-16

Release 6.3.1 is a GA release.

This document describes the changes in release 6.3.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-2904 Document MaxScale performance tuning

Bug fixes

  • MXS-4132 router_options=master ignores rank for first server

  • MXS-4121 MaxCtrl is limited to 2GB of memory

  • MXS-4120 Avrorouter crash with a SEQUENCE engine table

  • MXS-4113 namedserverfilter does not work with targets parameter

  • MXS-4112 python mariab can cause maxsccale to crash

  • MXS-4111 Extra warnings logged even with use_sql_variables_in=master

  • MXS-4110 Schemarouter does not ignore the sys schema

  • MXS-4109 The /user/inet endpoint fails schema validation

  • MXS-4101 Unexpected result with mixed 10.2 and 10.6 backends

  • MXS-4099 Crash with match/exclude in kafkacdc

  • MXS-4096 Binlog Routers SHOW SLAVE STATUS does not show SSL information

  • MXS-4095 Maxscale CDC to Kafka job is failing for few tables

  • MXS-4092 schemarouter: duplicate tables found, if table differs on upper lower case only

  • MXS-4091 Maxscale Redis | Spyder Deployments are failing (OperationalError: (2013, 'Lost connection to MySQL server during query'))

  • MXS-4088 The parameter's tooltip shows unnecessary attributes

  • MXS-4086 REST API allows deletion of last user

  • MXS-4084 Client port is not in 'maxctrl show sessions' output

  • MXS-4059 Make query editor visualization feature easier to use

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.0 Release Notes -- 2022-06-09

Release 6.4.0 is a GA release.

This document describes the changes in release 6.4.0, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4152 Schemarouter performance degrades as the number of tables increases

  • MXS-4151 Schemarouter duplicate checks are excessively slow

  • MXS-4139 connection_keepalive sends pings even if client is idle

  • MXS-4138 Race condition in binlogrouter

  • MXS-4134 /etc/maxscale.cnf.d/ is not created by package installation

  • MXS-4115 Maxscale prints user/pass with CHANGE MASTER command in logfile while failover.

  • MXS-4113 namedserverfilter does not work with targets parameter

  • MXS-4105 Queries on already established connections hanging for 15min when Redis server disconnected hard

  • MXS-4100 connection_keepalive=0 causes a memory leak

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.1 Release Notes -- 2022-07-14

Release 6.4.1 is a GA release.

This document describes the changes in release 6.4.1, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4193 HTTPS requests don't include Path=/ in cookies

  • MXS-4185 The state of the bootstrap nodes is not updated properly

  • MXS-4181 MaxScale w/SSL doesn't work on FIPS RHEL7

  • MXS-4180 Some non-multi-statement queries are classified as multi-statement ones

  • MXS-4177 maxctrl call command leaves stale errors

  • MXS-4172 Hang in RWSplitSession::correct_packet_sequence

  • MXS-4171 Unmodifiable parameters aren't prevented from being modified

  • MXS-4170 Bad create monitor command leaves a ghost monitor

  • MXS-4169 Listeners created at runtime require ssl_ca_cert when it should not be required

  • MXS-4166 Filter diagnostics are not shown in maxctrl show filters

  • MXS-4165 Servers with priority=0 are selected as Master

  • MXS-4164 Debug assertion when cat session ends

  • MXS-4160 Galeramon doesn't work with max_slave_replication_lag

  • MXS-4148 Log warning if reverse name resolution takes significant time

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.10 Release Notes -- 2023-08-30

Release 6.4.10 is a GA release.

This document describes the changes in release 6.4.10, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4726 Session command response verification unnecessarily stores PS IDs for readconnroute

  • MXS-4717 information_schema is not invalidated as needed

  • MXS-4706 Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.11 Release Notes -- 2023-10-30

Release 6.4.11 is a GA release.

This document describes the changes in release 6.4.11, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

External CVEs resolved.

  • CVE-2022-1586 Fixed by MXS-4806 Update pcre2 to 10.42

  • CVE-2022-1587 Fixed by MXS-4806 Update pcre2 to 10.42

  • CVE-2022-41409 Fixed by MXS-4806 Update pcre2 to 10.42

  • CVE-2020-7105 Fixed by MXS-4757 Update libhiredis to 1.0.2.

  • CVE-2023-27371 Fixed by MXS-4751 Update libmicrohttpd to version 0.9.76

Bug fixes

  • MXS-4831 Missing SQL error in server state change messages

  • MXS-4827 Connection attributes are not shown in maxctrl show sessions

  • MXS-4826 Prevent running replication through MaxScale

  • MXS-4815 @@last_gtid and @@last_insert_id are treated differently

  • MXS-4814 GTIDs used by causal_reads=global cannot be reset without restarting MaxScale

  • MXS-4811 Error handling differences between running maxctrl directly or in a subshell

  • MXS-4810 --timeout doesn't work with multiple values in --hosts

  • MXS-4807 MaxScale does not always report the OS version correctly

  • MXS-4799 ConfigManager may spam the log with warnings

  • MXS-4797 NullFilter has not been extended to support all routing enumeration values.

  • MXS-4792 Semi-sync replication through MaxScale causes errors on STOP SLAVE

  • MXS-4790 Log version after log rotation

  • MXS-4788 Galeramon should use gtid_binlog_pos if gtid_current_pos is empty

  • MXS-4784 MaxScale log viewer GUI doesn't automatically scroll to bottom

  • MXS-4782 Kafkacdc logs warnings about the configuration

  • MXS-4781 cooperative_replication works even if cluster parameter is not used

  • MXS-4780 Shutdown may hang if cooperative_replication is used

  • MXS-4779 Maxscale monitor suddenly loses entire cluster status (galeramon)

  • MXS-4778 Aborts due to SystemD watchdog should tell if a DNS lookup was in progress

  • MXS-4777 Maxscale crash due to systemd timeout

  • MXS-4775 KafkaCDC: current_gtid.txt is moving but is behind

  • MXS-4772 Config sync status leaves origin field empty on restart

  • MXS-4771 Problem while linking libnosqlprotocol.so

  • MXS-4766 maxctrl create report cannot write to a pipe

  • MXS-4765 Serialization of regular expressions doesn't add escaping slashes

  • MXS-4760 Automatically ignored tables are not documented for schemarouter

  • MXS-4749 log_throttling should be disabled if log_info is on

  • MXS-4747 log_throttling is hard to modify via MaxCtrl

  • MXS-4738 The fact that disable_master_failback does not work with root_node_as_master is not documented

  • MXS-4735 Connection IDs are missing from error messages

  • MXS-4732 MaxScale shutdown is not signal-safe

  • MXS-4724 slave_selection_criteria should accept lowercase version of the values

  • MXS-4707 The match parameters are not regular expressions

  • MXS-4562 When MaxScalle is installed from tarball and starded without -d option --basedir=. is not parsed properly and full directory needs to be specified

  • MXS-4538 No valid servers in cluster 'MariaDB-Monitor'

  • MXS-4457 Duplicate values in servers are silently ignored

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.12 Release Notes -- 2023-11-03

Release 6.4.12 is a GA release.

This document describes the changes in release 6.4.12, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4847 Crash on maxctrl list sessions

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.13 Release Notes -- 2023-11-30

Release 6.4.13 is a GA release.

This document describes the changes in release 6.4.13, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4856 GUI failed to create a monitor in a monitored server detail page

  • MXS-4798 Broken slave promoted to master when no other servers are available

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.14 Release Notes -- 2024-02-09

Release 6.4.14 is a GA release.

This document describes the changes in release 6.4.14, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-4862 ssl_version should specify minimum version

Bug fixes

  • MXS-4956 Session commands ignore delayed_retry_timeout

  • MXS-4947 Tables in information_schema are treated as a normal tables

  • MXS-4945 GUI doesn't validate object name uniqueness accurately

  • MXS-4934 Use-after-free after service deletion

  • MXS-4926 History length of sessions is not visible in the REST-API

  • MXS-4924 Very fast client and server may end up busy-looping a worker

  • MXS-4923 The "New messages available" button in the GUI Logs Archive does not disappear after being clicked.

  • MXS-4922 Memory growth for long-running sessions that use COM_CHANGE_USER

  • MXS-4921 Memory growth for long-running sessions that use prepared statements

  • MXS-4913 Memory leak when closing SSL connection

  • MXS-4912 Query classifier cache total-size book-keeping may be wrong

  • MXS-4910 readconnroute performance regression in 6.4

  • MXS-4908 Undefined behavior with module commands that take no arguments

  • MXS-4906 MonitorWorker::call_run_one_tick() called more often than intended

  • MXS-4900 maxctrl show qc_cache can easily overwhelm MaxScale

  • MXS-4896 Reducing the size of the query classifier cache does not cause excess entries to be freed.

  • MXS-4895 QC cache memory accounting on CentOS 7 is wrong

  • MXS-4865 5.5.5- prefix should not be added if all backends are MariaDB 11

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.15 Release Notes -- 2024-03-11

Release 6.4.15 is a GA release.

This document describes the changes in release 6.4.15, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-5007 Top-level service reconnection may cause a use-after-free

  • MXS-5000 insertstream uses an error code from the reserved client range

  • MXS-4998 MaxScale may send two COM_QUIT packets

  • MXS-4997 MaxScale: BUILD/install_build_deps.sh: deprecated --force-yes

  • MXS-4981 Hang on shutdown when large batches of session command are pending

  • MXS-4979 COM_CHANGE_USER may leave stale IDs to be checked

  • MXS-4978 Read-only transactions are incorrectly tracked

  • MXS-4967 Log throttling is sometimes disabled too early

  • MXS-4943 delayed_retry timeout errors do not have enough information

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.2 Release Notes -- 2022-09-02

Release 6.4.2 is a GA release.

This document describes the changes in release 6.4.2, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4258 Add permission for SHOW DATABASES for Xpand Service to work

  • MXS-4240 MXS-4239 readconnroute module routing read queries to inconsistent slave node

  • MXS-4239 Maxscale shows replication status as [Slave, Running] even when replication credentials are wrong

  • MXS-4237 Schemarouter duble free crash

  • MXS-4219 Settings of bootstrap servers are not correctly propagated to dynamic servers

  • MXS-4218 Configuration synchronization fails if static global parameters are different

  • MXS-4211 MaxScale throws std::out_of_range on invalid listener parameter

  • MXS-4209 KILL command doesn't work correctly if persistent connections are enabled

  • MXS-4198 MaxScale fails to validate its own certificate when the chain of trust is unknown to OpenSSL

  • MXS-4196 Readconnroute load balancing behavior is not well documented

  • MXS-4183 Multiplexing fails with "Timed out when waiting for a connection"

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.3 Release Notes -- 2022-10-14

Release 6.4.3 is a GA release.

This document describes the changes in release 6.4.3, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4321 Error from missing --secure option is not helpful

  • MXS-4313 MaxCtrl misinterprets some arguments

  • MXS-4312 REST API accepts empty resource IDs

  • MXS-4307 Parser can't recognize convert function parameters and cause wrong routing decision

  • MXS-4304 MariaDB-Monitor spams log with connection errors if server is both [Maintenance] and [Down]

  • MXS-4290 Maxscale masking filter returns parsing error on SELECT with very long WHERE

  • MXS-4289 Transaction starts on wrong server with autocommit=0

  • MXS-4283 Race condition in KILL command processing

  • MXS-4282 Servers that are [Down] may have [Slave of External Server]

  • MXS-4280 qc_sqlite does not properly handle a LIMIT clause

  • MXS-4279 "sub" field not set for JWTs

  • MXS-4275 MaxScale tries to start up if --export-config is used and a cached cluster configuration is present

  • MXS-4269 UPDATE with user variable modification is treated as a session command

  • MXS-4267 NULL values are exported as empty strings when using CSV format

  • MXS-4260 Maxscale crashes frequently while performing load testing

  • MXS-4259 warning: [xpandmon] 'late' is an unknown sub-state for a Xpand node

  • MXS-4247 Listener created with encryption even if ssl=false is passed

  • MXS-4231 Sometimes the date and time are missing in the query log

  • MXS-4227 MaxCtrl incompatibility with MemoryDenyWriteExecute=true is not documented

  • MXS-4221 GUI does not show other services used by services

  • MXS-4156 Update documentation on required monitor privileges

  • MXS-4094 Allow empty token when client is replying to AuthSwitchRequest

  • MXS-4083 CPU utilization high on MaxScale host

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.4 Release Notes -- 2022-11-29

Release 6.4.4 is a GA release.

This document describes the changes in release 6.4.4, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4415 Warning for xpandmon for 'leaving' / 'late, leaving' being an unknown sub-state

  • MXS-4413 UPDATE with user variable breaks replication

  • MXS-4404 Maxscale: KafkaCDC writes to current_gtid.txt causes high disk utilisation.

  • MXS-4397 fields parameter breaks REST-API filtering

  • MXS-4393 Authentication failures during shard mapping are not handled correctly

  • MXS-4389 Crash in handleError

  • MXS-4388 LOAD DATA LOCAL INFILE and changing autocomit causing stuck

  • MXS-4372 MAXGUI - Out of memory in client PC browser.

  • MXS-4353 /maxscale/logs/data endpoint doesn't filter syslog contents correctly

  • MXS-4348 Full SASL support is not enabled for kafka modules

  • MXS-4317 Smartrouter interrupts the wrong query

  • MXS-3043 Database grants in user_accounts_file should add the database to the list of known databases

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.5 Release Notes -- 2023-01-13

Release 6.4.5 is a GA release.

This document describes the changes in release 6.4.5, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4474 MaxScale hangs with warning about "Worker 1 attempted to send a message to worker 1"

  • MXS-4471 Table selection doesn't tolerate node failures

  • MXS-4470 COM_INIT_DB isn't routed to all shards

  • MXS-4469 Schemarouter routing logic documentation is out of date

  • MXS-4467 Explicit transactions without a default database do not work as expected with schemarouter

  • MXS-4460 Crash during query replay with service-to-service configuration

  • MXS-4454 Schemarouter should prefer targets which have databases in them for session commands

  • MXS-4453 Schemarouter selects an invalid target for queries that do not target a specific shard

  • MXS-4450 6.4 no longer provides full certificate chain in TLS HELLO

  • MXS-4440 Lost connection to backend server: network error (server1: 104, Connection reset by peer)

  • MXS-4439 Maxscale is failing with Resource temporarily unavailable errors

  • MXS-4435 Log rotation causes errors in qlafilter

  • MXS-4423 Rebalancing is not always initiated from the affected worker/thread

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.6 Release Notes -- 2023-03-29

Release 6.4.6 is a GA release.

This document describes the changes in release 6.4.6, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4566 RHEL8 Packages for 23.02.1 and 22.08.5

  • MXS-4557 Binlogrouter breaks if event size exceeds INT_MAX

  • MXS-4556 Maxscale ignores lower_case_table_names=1 on config file

  • MXS-4555 Dynamic filter capabilities do not work

  • MXS-4552 "Unknown prepared statement handler" error when connection_keepalive is disabled on a readconnroute service

  • MXS-4547 Empty regex // is not treated as empty

  • MXS-4540 transaction replay retries repeatedly after failing checksum

  • MXS-4524 Wrong server version assumption

  • MXS-4515 MaxScale leaks sessions if they are closed when writeq throttling is enabled

  • MXS-4514 skip_name_resolve is not modifiable at runtime

  • MXS-4510 Uncaught exception in binlogrouter

  • MXS-4504 IP wildcard values are not permitted in host values while using data masking

  • MXS-4499 config_sync_cluster always uses the mysql database

  • MXS-4494 Replication breaks if binlogfilter excludes events

  • MXS-4489 PHP program reports different collation_connection when connecting via Maxscale

  • MXS-4481 Attempting to create a table with the name "DUAL" crashes MaxScale

  • MXS-4476 Memory leak in smartrouter

  • MXS-4473 Hang in smartrouter under heavy load

  • MXS-4459 Improve match/exclude documentation for avrorouter and kafkacdc

  • MXS-4410 QLA filter not properly logging USE DBx command.

  • MXS-4197 pinloki_start_stop is unstable

  • MXS-3972 The rpl_state in binlogrouter is not atomic

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.7 Release Notes -- 2023-05-24

Release 6.4.7 is a GA release.

This document describes the changes in release 6.4.7, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4615 Partially executed multi-result queries are not treated as partial results

  • MXS-4614 Query classifier does not recognize BEGIN NOT ATOMIC ... END

  • MXS-4611 Readwritesplit prefers idle primary over busy replicas

  • MXS-4602 Qlafilter logs responses from non-matched queries

  • MXS-4599 AVX instructions end up being executed on startup

  • MXS-4596 Query canonicalization does not work on scientific numbers

  • MXS-4595 maxctrl classify sends malformed SQL

  • MXS-4586 transaction_replay_max_size default is 1GiB instead of 1MiB

  • MXS-4560 Not all passwords were obfuscated in the maxctrl report

  • MXS-4551 qlafilter with options=extended does not log query nor date

  • MXS-4550 Regular expression documentation is inaccurate and lacking

  • MXS-4548 The statement canonicalizer cannot handle comments within statements

  • MXS-4502 KB pages reference mysqlauth and mysqlauth is deprecated for mariadbauth

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.8 Release Notes -- 2023-07-31

Release 6.4.8 is a GA release.

This document describes the changes in release 6.4.8, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

New Features

  • MXS-4541 Provide a way to show details about all supported MaxScale modules via REST API and/or MaxCtrl

Bug fixes

  • MXS-4683 ssl parameters specified on the bootstrap server are not copied to the rest

  • MXS-4676 REST-API documentation is wrong about which server parameters can be modified

  • MXS-4666 causal_reads=local is serialized as causal_reads=true

  • MXS-4665 Listener creation error is misleading

  • MXS-4664 xpandmon diagnostics are not useful

  • MXS-4662 Galeramon use_priority example is incorrect

  • MXS-4661 Document supported wire protocol versions

  • MXS-4659 Cache filter hangs if statement consists of multiple packets.

  • MXS-4658 Post reboot binlog router entered stuck state

  • MXS-4657 Add human readable message text to API errors like 404

  • MXS-4656 Setting session_track_trx_state=true leads to OOM kiled.

  • MXS-4651 Documentation claims that netmask support is limited to numbers 255 and 0

  • MXS-4648 MongoDB monitoring promoted when connecting to NoSQL service

  • MXS-4645 qlafilter log event notifications are sometimes lost

  • MXS-4643 GUI is unable to create a listener with other protocols than MariaDBProtocol

  • MXS-4634 readconnroute documentation page contains a typo "max_slave_replication_lag"

  • MXS-4631 Harden BLR binlog file-index handling

  • MXS-4628 Connection in Query Editor is closed after 1 hour of being idle

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL

MariaDB MaxScale 6.4.9 Release Notes -- 2023-08-21

Release 6.4.9 is a GA release.

This document describes the changes in release 6.4.9, when compared to the previous release in the same series.

If you are upgrading from an older major version of MaxScale, please read theupgrading document for this MaxScale version.

For any problems you encounter, please consider submitting a bug report on our Jira.

Bug fixes

  • MXS-4722 Case-sensitiveness of enumerations is not documented

  • MXS-4721 Galeramon does not update replication lag of replicating servers

  • MXS-4720 Implement an option to switch to the old "ping" behaviour in MaxScale

  • MXS-4719 Connection init sql file execution can hang

  • MXS-4714 qc_sqlite does not properly parse a RENAME statement

  • MXS-4708 Update maxscale.cnf default file

  • MXS-4704 SHOW TABLE STATUS FROM some_schema Fails with SchemaRouter

  • MXS-4701 GTID update may block the REST-API

  • MXS-4700 Binlogrouter treats GTID sequences as 32-bit integers

  • MXS-4696 Readwritesplit does not detect unrecoverable situations

  • MXS-4695 Binlogrouter always opens a new binlog on startup

  • MXS-4691 Binlogrouter cannot write binlog files larger than 4GiB

  • MXS-4690 Binlogrouter runs out of memory on very large transactions

  • MXS-4684 Detect ALTER EVENT failure on MariaDB 11.0

  • MXS-4681 Encrypted passwords are persisted in plaintext

  • MXS-4680 Session idleness diagnostic is wrong

  • MXS-4677 MaxScale BinlogRouter skips large transactions causing data Inconsistency on attached slave

  • MXS-4675 Switchover fails with 'Unknown thread id' error

  • MXS-4672 Document grants needed for MariaDB 11.1

  • MXS-4613 binlogrouter shows MaxScale's binary log coordinates in SHOW SLAVE STATUS

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the supported Linux distributions.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.

This page is licensed: CC BY-SA / Gnu FDL