Release 23.08.10 is a GA release.
This document describes the changes in release 23.08.10, 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.
MXS-5618 Maxctrl interactive mode doesn't use --tls-verify-server-cert=false
MXS-5613 The logout screen is shown when accessing the MaxGUI login view.
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-5597 admin_oidc_url is documented to not be dynamic when in fact it is
MXS-5590 REST-API always sends a Connection: close header
MXS-5588 Signal 11 crash when enabling causal reads with Galera
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
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
Release 23.08.9 is a GA release.
This document describes the changes in release 23.08.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.
MXS-5533 Remove session_trace parameter from services section
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-5522 config sync does not ignore port for listeners
MXS-5520 config_sync_password infinitely doubles after maxscale restart & alter command
MXS-5518 Documentation of switchover-force lacks warnings
MXS-5511 The Contact view in the GUI has outdated information
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-5493 Cluster tree is not visualized accurately
MXS-5492 idle_session_pool_time=0s does not fairly share connections
MXS-5488 Need Documentation updates for Maxscale install recommendation
MXS-5481 Galera Monitor does not log an error if "SHOW SLAVE STATUS" fails
MXS-5480 disable_sescmd_history=true causes a use-after-free
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-5430 Authentication errors are sometimes not read if backend TLS is enabled
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-5409 list session in GUI shows wrong amount of sessions
MXS-5408 rebuild-server does not work with MariaDB 11.4
MXS-5404 The monitor journal file is not discarded aggressively enough.
MXS-5403 Debug assertion on very large binary protocol prepared statements
MXS-5402 Monitor connections do not check SSL certificate host even when ssl_verify_peer_host is enabled for the server
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
MXS-5366 Certain special characters in the maxscale user causes async-rebuild-server to fail
MXS-5340 ed25519 socket droped when no user_mapping_file
MXS-5314 Resultset table not fully expanded for inactive query tab
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.8 is a GA release.
This document describes the changes in release 23.08.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.
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
MXS-5177 Introduce a new core_file variable in MaxScale
MXS-5398 Some log messages are not logged when session_trace is used
MXS-5394 Empty passwords are shown as non-empty if password encryption is enabled
MXS-5387 Crash in MariaDBParser::Helper::get_query_info()
MXS-5383 Alter table editor failed to assign table's collation value
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-5364 Allow monitor ssh-parameters to be modified at runtime
MXS-5363 GDB stacktraces may hang
MXS-5361 Query editor: Column visibility filter shows wrong checkboxe values after search
MXS-5359 Transaction replay may deadlock with switchover
MXS-5357 Improve MariaDB Monitor documentation on auto_failover and auto_rejoin
MXS-5356 Readwritesplit master_reconnection is incompatible with GET_LOCK
MXS-5355 Switchover may cause two transaction replays to be started
MXS-5351 XA ROLLBACK is not treated as a rollback in MaxScale
MXS-5350 XA END is treated as the transaction commit instead of XA PREPARE
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-5338 Maxscale Admin Audit file should include ip address or host of calling session
MXS-5315 maxctrl destroy session takes only one ID as argument
MXS-5307 MaxScale kafkacdc logs "notice : Started replicating from [x.x.x.x]:3306 at GTID 'N-N-N' at every timeout/reconnection
MXS-5302 Prepared statements should never be removed from session command history
MXS-5298 Kafkacdc always reads last GTID from Kafka on startup
MXS-5296 New entity table is added without default collation
MXS-5273 The --config-check fails if /var/cache/maxscale cannot be read
MXS-5272 Monitor does not show broken external replication in "maxctrl list servers"
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-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-5229 Master Stickiness status not displayed correctly with use_priority
MXS-5178 Replicas after maxscale binlog don't get updates
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.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.7 is a GA release.
This document describes the changes in release 23.08.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.
MXS-5234 webpack warns about yargs
MXS-5232 Large batches of session commands may leave sessions alive for a long time
MXS-5231 Connections to servers in maintenance are sometimes not discarded
MXS-5227 MaxScale does not drop supplementary groups if --user is used
MXS-5226 LICENSE.TXT is a dangling symlink in RPMs
MXS-5222 Query Editor: Unable to fully see error result when previewing a table
MXS-5221 Query Editor: Unable to visualize preview data result set
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-5208 Table header row fails to expand to full width in ERD modeler
MXS-5206 Readwritesplit does not drop connections to severely lagging servers
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-5190 dotnet EntityFrameworkCore generates insert queries that are getting routed to all nodes as session write
MXS-5171 MaxScale does not have time to open the file during rotation for a new binlog
MXS-5167 Query Editor "Filter By" and "Group By" work improperly
MXS-5162 Post reboot binlog router entered stuck state
MXS-5161 Downgrading to 23.08 from 24.02 removes some required directories
MXS-5160 postinst script prints output while installing
MXS-5159 MaxScale does not use remote address sent in proxy header from client for authenticating the client
MXS-5146 23.08.6 build ppc64le fails
MXS-5135 The GUI should clear all http readonly cookies
MXS-5133 Memory leak in namedserverfilter
MXS-5132 Inbound proxy protocol does not generate the correct error if proxy_protocol_network is not defined
MXS-5131 comment filter uses the wrong module name
MXS-5127 DEALLOCATE PREPARE is not routed to all nodes
MXS-5126 Segfault in cache filter with default configuration
MXS-5125 Executing identical prepared statements may lose one of them on reconnection
MXS-5121 MaxScale detects wrong server character set
MXS-5109 A logout endpoint for the GUI to clear all http readonly cookies
MXS-4605 Monitor should drop the connection when faced with an Access Denied error
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.6 is a GA release.
This document describes the changes in release 23.08.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.
MXS-5067 Add "enforce_read_only_servers" feature to MariaDB Monitor
MXS-5106 Server version checks are overly pessimistic
MXS-5101 MariaDB Monitor can kill connections from other monitors during switchover
MXS-5095 Master Stickiness state is not documented
MXS-5094 Stacktraces fail to be generated when MaxScale is run from the terminal
MXS-5093 SQL API does not return binary data in resultsets
MXS-5091 admin_audit file name does not use log_dir value
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-5068 users_refresh_time=0s does not work as documented
MXS-5063 Maxscale crash - "terminate called after throwing an instance of 'std::bad_alloc'"
MXS-5051 cmake does not check for unixodbc-dev
MXS-5048 Problem in hostname matching when using regex (%) for user authentication
MXS-5046 maxctrl alter admin_ssl_* not actually updating
MXS-5039 cooperative_monitoring_locks can leave stale locks on a server if network breaks
MXS-5038 Maxscale key limitations
MXS-5035 Setting a path argument to empty reads uninitialized memory
MXS-5034 REST-API TLS keys are not validated at runtime
MXS-5033 MaxScale should prevent incompatible TLS certificates from being configured
MXS-5031 enforce_read_only_slaves can set master to read_only
MXS-5023 kill user and transaction_replay don't play well together in Galera cluster
MXS-5021 gdb-stacktrace is incorrectly presented as a debug option
MXS-5010 Session commands that are executed early are not validated
MXS-5006 maxscale crash
MXS-4964 Simple sharding tutorial is out of date
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
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.5 is a GA release.
This document describes the changes in release 23.08.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.
CVE-2023-1667 Fixed by MXS-5011 Upgrade libssh to 0.10.6
CVE-2023-2283 Fixed by MXS-5011 Upgrade libssh to 0.10.6
CVE-2023-6004 Fixed by MXS-5011 Upgrade libssh to 0.10.6
CVE-2023-6918 Fixed by MXS-5011 Upgrade libssh to 0.10.6
CVE-2023-48795 Fixed by MXS-5011 Upgrade libssh to 0.10.6
MXS-4917 Add disk_space_ok option to master_conditions and slave_conditions
MXS-5008 Log message on releasing exclusive locks when no lock majority is confusing
MXS-5007 Top-level service reconnection may cause a use-after-free
MXS-5001 Maxscale fail to initiate maxscale.service (Missing /var/run/maxscale) directory
MXS-4998 MaxScale may send two COM_QUIT packets
MXS-4997 MaxScale: BUILD/install_build_deps.sh: deprecated --force-yes
MXS-4996 Order of servers is different after restart if runtime modifications have been done
MXS-4995 The "static" property of an object is lost upon restart
MXS-4994 Multiple warnings from the REST-API are printed on the same line
MXS-4992 Documentation Link in GUI leads to 404 page not found
MXS-4988 maxscale doesn't properly close connections for TCP health check probes
MXS-4982 OpenSSL system call error is logged as ERROR when client disconnects abruptly
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-4969 Can't create more than max_prepared_stmt_count statements
MXS-4968 REST-API TLS certificates can be reloaded but the path to them cannot be altered
MXS-4967 Log throttling is sometimes disabled too early
MXS-4961 Result of KILL CONNECTION_ID() does not propagate all the way to the client
MXS-4956 Session commands ignore delayed_retry_timeout
MXS-4948 Unable to see columns of view in the Query Editor
MXS-4947 Tables in information_schema are treated as a normal tables
MXS-4945 GUI doesn't validate object name uniqueness accurately
MXS-4943 delayed_retry timeout errors do not have enough information
MXS-4935 False protocol incompatibility error
MXS-4934 Use-after-free after service deletion
MXS-4930 'maxctrl reload tls' has the usage of 'maxctrl reload service'
MXS-4926 History length of sessions is not visible in the REST-API
MXS-4925 self link in /maxscale/logs/data is off by one page
MXS-4924 Very fast client and server may end up busy-looping a worker
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-4914 GUI dashboard's width is reduced unexpectedly
MXS-4912 Query classifier cache total-size book-keeping may be wrong
MXS-4910 readconnroute performance regression in 6.4
MXS-4907 Nested parameters in PATCH /v1/maxscale/ do not work correctly
MXS-4906 MonitorWorker::call_run_one_tick() called more often than intended
MXS-4903 Bad configuration in PATCH may partially configure monitors
MXS-4901 Turning on log_info causes parsing related errors and warnings
MXS-4900 maxctrl show qc_cache can easily overwhelm MaxScale
MXS-4898 MaxScale sends wrong character set (session tracking)
MXS-4896 Reducing the size of the query classifier cache does not cause excess entries to be freed.
MXS-4893 Query history retention period increases unexpectedly every time the setting dialog is opened
MXS-4891 Query editor schema explorer is disabled after reconnecting connections
MXS-4888 Unable to type custom row limit in the Query configuration dialog
MXS-4879 Transaction state viewed from the session is different from the transaction state as viewed from RWS.
MXS-4865 5.5.5- prefix should not be added if all backends are MariaDB 11
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.4 is a GA release.
This document describes the changes in release 23.08.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.
MXS-4862 SSL_VERSION should have a way to disallow deprecated versions
MXS-4881 Startup option --basedir mishandled
MXS-4869 Parameter table isn't refreshed after update in the GUI
MXS-4866 GUI doesn't show and allow to edit connection_metadata after a listener is created
MXS-4858 maxscale 23.08.3 crash with dump_last_statements=on_close set
MXS-4856 GUI failed to create a monitor in a monitored server detail page
MXS-4855 While writing query GUI response very slow
MXS-4851 No space or separator between 2 routing targets in the services dashboard
MXS-4818 Columns with the same name break sorting, filtering, and grouping features in Query Editor
MXS-4798 Broken slave promoted to master when no other servers are available
MXS-4789 GUI workspace caching doesn't work accurately
MXS-4728 Laggy issues on result data table
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.3 is a GA release.
This document describes the changes in release 23.08.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.
MXS-4847 Crash on maxctrl list sessions
MXS-4844 Relative paths do not work when defined in the configuration file
MXS-4803 Binlog encryption broken
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.2 is a GA release.
This document describes the changes in release 23.08.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.
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
MXS-4759 Force failover flag
MXS-4831 Missing SQL error in server state change messages
MXS-4829 Query Editor doesn't assign active database to existing query tabs
MXS-4822 Chart pane width issue in Query Editor
MXS-4821 Multi-statement detection works differently on non-AVX2 CPUs
MXS-4817 maxscale crashes on maxsimd::generic::is_multi_stmt_imp
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-4812 More than one primary database in a monitor results in errors in MaxScale GUI
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-4808 connection_metadata checks for the wrong capability bit
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-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-4778 Aborts due to SystemD watchdog should tell if a DNS lookup was in progress
MXS-4777 Maxscale crash due to systemd timeout
MXS-4776 Sescmd target selection is sub-optimal with lazy_connect
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-4750 dynamic_node_detection=false does not work with server hostname, needs IP
MXS-4743 switchover-force should ignore replication delay
MXS-4718 Add replication_custom_options to enable replication TLS certification check
MXS-4686 Undefined behavior in ed25519 plugin
MXS-4604 Qlafilter doesn't handle pipelined queries correctly
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
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.1 is a GA release.
This document describes the changes in release 23.08.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.
CVE-2023-27371 Fixed by MXS-4751 Update libmicrohttpd to version 0.9.76
MXS-3761 Visualize response_time_distribution
MXS-3753 Add option to run PAM authentication in a suid sanbox
MXS-4762 REST-API generates too many errors for some endpoints
MXS-4760 Automatically ignored tables are not documented for schemarouter
MXS-4749 log_throttling should be disabled if log_info is on
MXS-4735 Connection IDs are missing from error messages
MXS-4724 slave_selection_criteria should accept lowercase version of the values
MXS-4723 Passthrough authentication does not support COM_CHANGE_USER
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL
Release 23.08.0 is a Beta release.
This document describes the changes in release 23.08, when compared to release 23.02.
For any problems you encounter, please consider submitting a bug report on our Jira.
During switchover, MariaDB-Monitor creates a new connection to the master with
a long timeout, ignoring the limit of backend_read_timeout. This reduces the
probability of long commands such as set global read_only=1 timing out. When
kicking out super and read-only admin users, monitor prevent writes with
"flush tables with read lock". Seemonitor documentation
for more information.
Earlier when the SQL sent by a client was logged due to log_info being enabled,
the SQL was logged verbatim, which would cause the log to contain extra newlines
in case the SQL did. From 23.08 forward, newlines are replaced with the text ,
so that a logged line will not contain any extra newlines.
connection_timeout renamed to wait_timeoutThe connection_timeout parameter was renamed to wait_timeout and the old
name is now an alias to the new name. The use of the old name is deprecated.
max_slave_replication_lag renamed to max_replication_lagThe Readwritesplit max_slave_replication_lag parameter was renamed tomax_replication_lag and the old name is now an alias for the new name.
The use of the old name is deprecated.
The configuration parameters query_classifier and query_classifier_args
have been deprecated and are ignored.
The strip_db_esc parameter is deprecated and will be removed in a future
release. The default behavior of stripping escape characters is in all known
cases the correct thing to do and as such this parameter is never required.
The PCRE2 library used by MaxScale now limits the heap memory to 1GB and the
matching limit to 500000 matches. This change was done to prevent catastrophic
backtracing that occurred when regular expressions used nested recursion
e.g. SELECT.*.*FROM.*.*t1.
The NoSQL protocol module now supports internal caching. Since this cache uses keys created from NoSQL protocol requests and stores NoSQL protocol responses, it is more efficient than the regular cache filter. More information about this functionality can be foundhere.
This version of switchover performs the switch even if the primary server is unresponsive i.e. responds to pings but does not perform any commands in a reasonable time. May lead to diverging replication on the old primary. Seemonitor documentation for more information.
The causal_reads=fast_universal mode uses the same mechanism to retrieve the
GTID position that the universal mode uses but behaves like the fast mode
when routing queries.
The schemarouter database map cache can now be manually cleared with a MaxCtrl command:
maxctrl call command schemarouter clear <service>This makes it possible to schedule the clearing of the caches for busy systems where the update of the map takes a long time.
Stale entries in the schemarouter database map can now be used up tomax_staleness seconds. This reduces the impact that a shard update causes to
the client applications.
When the service password is changed, MaxScale will remember and use the previous password if the new does not work. This makes it easier to manage the changing of the password, as the password in the backend and in MaxScale need not be changed simultaneously. More information about this functionality can be foundhere.
iss field in JWTsThe iss field of the JWTs that the REST-API in MaxScale generates can now be
configured with admin_jwt_issuer. This allows REST-API clients to see who
issued the token.
It is now possible to specify options in an include-section, to be included by other sections. This is useful, for instance, if there are multiple monitors that otherwise are identically configured, but for their list of servers. More information about this functionality can be foundhere.
The new transaction_replay_safe_commit variable controls whether
about-to-commit transaction are replayed when transaction_replay is
enabled. The new default is to not replay transactions that were being committed
when the connection to the server was lost.
Passthrough authentication mode for MariaDBAuth-module. Seeauthenticator documentation for more information.
If a query in a transaction is interrupted and the result was partially delivered to the client, readwritesplit will now retry the execution of the query and discard the already delivered part of the result.
The LDI filter adds support for LOAD DATA LOCAL INFILE
from S3 compatible storage.
The new connection_metadata listener parameter controls the set of metadata
variables that are sent to the client during connection creation.
By default the values of the system variables character_set_client,character_set_connection, character_set_results, max_allowed_packet,system_time_zone, time_zone and tx_isolation are sent as well as the
current number of connections as the threads_connected variable and the real
64-bit connection ID as connection_id.
Compatible MariaDB connectors will use this information from MaxScale instead of querying the values of the variables from the database server which greatly speeds up connection creation.
It is now possible to limit the nodes the Xpand monitor dynamically detects to those residing in a specific region. See region_name and region_oid for more information.
Numerous additions have been added and improvements made to MaxGUI. The most notable ones are listed here:
MXS-4364 Auto choose active schema for new query tab.
There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.
RPM and Debian packages are provided for the supported Linux distributions.
Packages can be downloaded here.
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.
CC BY-SA / Gnu FDL