MaxScale 25.01 MariaDB MaxScale Enterprise 25.01.2 Release Notes
MariaDB MaxScale Enterprise 25.01.2 Release Notes
Release 25.01.2 is a GA release.
This document describes the changes in release 25.01.2, 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.
External CVEs resolved.
- CVE-2023-39410 Fixed by MXS-5454 Update avro-c to 1.11.4
Bug fixes
- MXS-5542 kafkacdc commits offsets when it probes GTIDs from Kafka
- MXS-5541 Logs Archive page doesn't show useful API error
- MXS-5535 Not all parameters are shown when creating a new object in the GUI
- MXS-5534 maxpostprocess and maxvisualize do not work when used from a binary tarball
- MXS-5533 Remove session_trace parameter from services section
- MXS-5532 Diff does not detect anomalous configuration
- MXS-5531 Binary tarballs include experimental modules
- MXS-5530 Default value of wait_timeout should be the same as in MariaDB
- MXS-5529 Session commands with max_slave_connections=0 after switchover do not discard stale connections
- MXS-5528 Diff router is not compatible with config-sync
- MXS-5527 The "INSERT INTO...RETURNING" syntax breaks causal_reads
- MXS-5522 config sync does not ignore port for listeners
- MXS-5521 Crash in diff router
- MXS-5520 config_sync_password infinitely doubles after maxscale restart & alter command
- MXS-5519 Documentation regarding mixing of cooperative_monitoring_locks and passive is unclear
- MXS-5518 Documentation of switchover-force lacks warnings
- MXS-5513 Config Wizard page is accessible by
basic
user - MXS-5511 The Contact view in the GUI has outdated information
- MXS-5510 Upgrading to 25.01.1 causes systemd service files to be removed
- MXS-5509 WCAR visualization is not included in the package
- 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-5505 Revert 60400ee256 MXS-4685: Seek GTIDs incrementally
- MXS-5493 Cluster tree is not visualized accurately
- MXS-5492 idle_session_pool_time=0s does not fairly share connections
- MXS-5490 Address field unexpectedly auto-truncates on the GUI dashboard
- MXS-5488 Need Documentation updates for Maxscale install recommendation
- MXS-5485 Reads are not retried if connection creation fails due to sub-service failure
- MXS-5484 Binlogrouter multidomain support broken in 24.02
- 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-5476 "maxctrl alter monitor MyMonitor auto_failover=true" fails
- MXS-5471 GUI reference doc links are broken
- MXS-5468 use-after-free when stopping capture
- MXS-5467 Parallel query execution fails when multiple query tabs are open
- MXS-5466 MaxCtrl warnings are very verbose
- MXS-5464 Result headers are not fully expanded in the inactive tab when running queries parallelly
- MXS-5463 GUI Logs Archive doesn't display latest log on second visit without refresh
- MXS-5462 Preserve timestamp when compressing files in Binlogrouter
- MXS-5455 Errors during loading of users lack the service name
- MXS-5451 GUI tooltip persists on screen after page navigation
- 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-5441 Dropdown inputs in Query Editor table editor are not focusable
- MXS-5437 Failed authentication warnings do not mention lack of client-side SSL as the reason of the failure
- MXS-5404 The monitor journal file is not discarded aggressively enough.
- MXS-5340 ed25519 socket droped when no user_mapping_file
- MXS-5314 Resultset table not fully expanded for inactive query tab
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.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.