MaxScaleのBSLバージョン情報

最終更新日 : 2025-06-11

MaxScaleにおいてBSLが適用されるバージョン情報について記載しています。

出典元

• MariaDB MaxScale
• github – MaxScale

【各バージョンのBSLライセンス適用状況】

Version	Minor Version	License	Release Date	Change License Date
2.4	2.4.0	GPL	2019-06-29	2023-01-01
2.4	2.4.1	GPL	2019-08-20	2023-01-01
2.4	2.4.2	GPL	2019-08-30	2023-01-01
2.4	2.4.3	GPL	2019-11-06	2023-10-29
2.4	2.4.4	GPL	2019-11-13	2023-10-29
2.4	2.4.5	GPL	2019-12-21	2023-12-18
2.4	2.4.6	GPL	2020-01-24	2024-01-15
2.4	2.4.7	GPL	2020-02-13	2024-02-10
2.4	2.4.8	GPL	2020-03-18	2024-03-10
2.4	2.4.9	GPL	2020-04-30	2024-04-23
2.4	2.4.10	GPL	2020-06-08	2024-06-02
2.4	2.4.11	GPL	2020-07-15	2024-07-07
2.4	2.4.12	GPL	2020-08-25	2024-08-24
2.4	2.4.13	GPL	2020-10-19	2024-10-14
2.4	2.4.14	GPL	2020-11-25	2024-11-16
2.4	2.4.15	GPL	2021-01-21	2025-01-18
2.4	2.4.16	GPL	2021-02-17	2025-02-16
2.4	2.4.17	GPL	2021-03-08	2025-03-08
2.4	2.4.18	BSL	2021-11-02	2025-10-29
2.4	2.4.19	BSL	2022-01-10	2026-01-04

Version	Minor Version	License	Release Date	Change License Date
2.5	2.5.0	GPL	2020-06-18	2024-06-15
2.5	2.5.1	GPL	2020-07-16	2024-07-16
2.5	2.5.2	GPL	2020-08-14	2024-07-16
2.5	2.5.3	GPL	2020-08-31	2024-08-24
2.5	2.5.4	GPL	2020-09-29	2024-09-25
2.5	2.5.5	GPL	2020-10-21	2024-10-14
2.5	2.5.6	GPL	2020-12-15	2024-11-26
2.5	2.5.7	GPL	2021-01-27	2025-01-25
2.5	2.5.8	GPL	2021-02-18	2025-02-16
2.5	2.5.9	GPL	2021-03-10	2025-03-08
2.5	2.5.10	GPL	2021-03-25	2025-03-24
2.5	2.5.11	GPL	2021-05-04	2025-04-28
2.5	2.5.12	GPL	2021-05-26	2025-05-25
2.5	2.5.13	GPL	2021-06-04	2025-05-25
2.5	2.5.14	GPL	2021-07-21	2025-05-25
2.5	2.5.15	BSL	2021-08-18	2025-08-17
2.5	2.5.16	BSL	2021-10-12	2025-10-11
2.5	2.5.17	BSL	2021-12-13	2025-12-13
2.5	2.5.18	BSL	2022-01-12	2026-01-04
2.5	2.5.19	BSL	2022-02-11	2026-02-11
2.5	2.5.20	BSL	2022-05-10	2026-05-03
2.5	2.5.21	BSL	2022-07-08	2026-07-07
2.5	2.5.22	BSL	2022-10-11	2026-10-04
2.5	2.5.23	BSL	2023-11-28	2026-11-16
2.5	2.5.24	BSL	2023-01-04	2027-01-04
2.5	2.5.25	BSL	2023-03-30	2027-03-14
2.5	2.5.26	BSL	2023-05-23	2027-05-22
2.5	2.5.27	BSL	2023-07-27	2027-07-24
2.5	2.5.28	BSL	2023-08-21	2027-08-18
2.5	2.5.29	BSL	2023-10-25	2027-10-10

Version	Minor Version	License	Release Date	Change License Date
21.06	6.0.0	BSL	2021-06-30	2025-06-21
21.06	6.1.0	BSL	2021-07-15	2025-07-14
21.06	6.1.1	BSL	2021-07-15	2025-07-14
21.06	6.1.2	BSL	2021-09-27	2025-09-20
21.06	6.1.3	BSL	2021-09-27	2025-09-20
21.06	6.1.4	BSL	2021-10-18	2025-10-11
21.06	6.2.0	BSL	2021-11-26	2025-11-19
21.06	6.2.1	BSL	2022-01-13	2026-01-04
21.06	6.2.2	BSL	2022-02-14	2026-02-11
21.06	6.2.3	BSL	2022-03-09	2026-03-08
21.06	6.2.4	BSL	2022-03-30	2026-03-08
21.06	6.3.0	BSL	2022-04-14	2026-04-08
21.06	6.3.1	BSL	2022-05-16	2026-05-03
21.06	6.4.0	BSL	2022-06-09	2026-06-06
21.06	6.4.1	BSL	2022-07-14	2026-07-11
21.06	6.4.2	BSL	2022-09-02	2026-08-25
21.06	6.4.3	BSL	2022-10-14	2026-10-04
21.06	6.4.4	BSL	2022-11-29	2026-11-16
21.06	6.4.5	BSL	2023-01-13	2027-01-13
21.06	6.4.6	BSL	2023-03-29	2027-03-14
21.06	6.4.7	BSL	2023-05-24	2027-05-22
21.06	6.4.8	BSL	2023-07-31	2027-07-24
21.06	6.4.9	BSL	2023-08-21	2027-08-18
21.06	6.4.10	BSL	2023-08-30	2027-08-18
21.06	6.4.11	BSL	2023-10-30	2027-10-10
21.06	6.4.12	BSL	2023-11-03	2027-10-10
21.06	6.4.13	BSL	2023-11-30	2027-11-30
21.06	6.4.14	BSL	2024-02-09	2028-01-30
21.06	6.4.15	BSL	2024-03-11	2028-02-27
21.06	21.06.16	GPL	2024-06-03	2024-06-03
21.06	21.06.17	GPL	2024-09-09	2024-06-03
21.06	21.06.18	GPL	2024-12-09	2024-06-03
21.06	21.06.19	GPL	2024-12-09	2024-06-03
21.06	21.06.20	GPL	2024-12-09	2024-06-03

Version	Minor Version	License	Release Date	Change License Date
22.08	22.08.0	BSL	2022-08-15	2026-08-08
22.08	22.08.1	BSL	2022-09-12	2026-09-06
22.08	22.08.2	BSL	2022-10-20	2026-10-04
22.08	22.08.3	BSL	2022-12-02	2026-11-16
22.08	22.08.4	BSL	2023-01-19	2027-01-19
22.08	22.08.5	BSL	2023-03-27	2027-03-14
22.08	22.08.6	BSL	2023-05-26	2027-05-22
22.08	22.08.7	BSL	2023-08-01	2027-07-24
22.08	22.08.8	BSL	2023-08-30	2027-08-18
22.08	22.08.9	BSL	2023-10-30	2027-10-10
22.08	22.08.10	BSL	2023-11-06	2027-10-10
22.08	22.08.11	BSL	2023-12-01	2027-11-30
22.08	22.08.12	BSL	2024-03-11	2028-02-27
22.08	22.08.13	BSL	2024-06-03	2025-09-12
22.08	22.08.14	BSL	2024-09-09	2025-09-12
22.08	22.08.15	BSL	2024-12-09	2025-09-12
22.08	22.08.16	BSL	2024-12-09	2025-09-12
22.08	22.08.17	BSL	2024-12-09	2025-09-12

Version	Minor Version	License	Release Date	Change License Date
23.02	23.02.0	BSL	2023-02-27	2027-02-21
23.02	23.02.1	BSL	2023-03-20	2027-03-14
23.02	23.02.2	BSL	2023-05-30	2027-05-22
23.02	23.02.3	BSL	2023-08-07	2027-07-24
23.02	23.02.4	BSL	2023-08-30	2027-08-18
23.02	23.02.5	BSL	2023-10-30	2027-10-10
23.02	23.02.7	BSL	2023-12-04	2027-11-30
23.02	23.02.8	BSL	2023-12-06	2027-11-30
23.02	23.02.9	BSL	2024-03-11	2028-02-27
23.02	23.02.10	BSL	2024-06-03	2026-03-20
23.02	23.02.11	BSL	2024-09-09	2026-03-20
23.02	23.02.12	BSL	2024-12-09	2026-03-20
23.02	23.02.13	BSL	2024-12-09	2026-03-20
23.02	23.02.14	BSL	2024-12-09	2026-03-20

Version	Minor Version	License	Release Date	Change License Date
23.08	23.08.0	BSL	2023-09-04	2027-08-18
23.08	23.08.1	BSL	2023-09-21	2027-09-19
23.08	23.08.2	BSL	2023-10-30	2027-10-10
23.08	23.08.3	BSL	2023-11-06	2027-10-10
23.08	23.08.4	BSL	2023-12-05	2027-11-30
23.08	23.08.5	BSL	2024-03-11	2028-02-27
23.08	23.08.6	BSL	2024-06-03	2026-09-21
23.08	23.08.7	BSL	2024-09-09	2026-09-21
23.08	23.08.8	BSL	2024-12-09	2026-09-21
23.08	23.08.9	BSL	2024-12-09	2026-09-21
23.08	23.08.10	BSL	2024-12-09	2026-09-21

Version	Minor Version	License	Release Date	Change License Date
24.02	24.02.0	BSL	2024-02-29	2028-02-27
24.02	24.02.1	BSL	2024-04-10	2028-04-03
24.02	24.02.2	BSL	2024-06-03	2027-04-10
24.02	24.02.3	BSL	2024-09-09	2027-04-10
24.02	24.02.4	BSL	2024-12-09	2027-04-10
24.02	24.02.5	BSL	2024-12-09	2027-04-10
24.02	24.02.6	BSL	2024-12-09	2027-04-10

【各バージョンにおいて修正されたバグ情報】

2.4.18

• MXS-3800 Not enough information in server state change messages
• MXS-3609 Some statistics use 32-bit integers
• MXS-3582 [readwritesplit] Failed to execute session command
• MXS-3538 Removal of authenticator_options is not documented in upgrade documents
• MXS-3535 user variable is not collected if it’s in join clause
• MXS-3533 MaxScale doesn’t advertise the SESSION_TRACK capability
• MXS-3529 Maxscale is not compatible with the latest cmake 3.20
• MXS-3487 Old master connection is left open after transaction migration
• MXS-3415 –export-config uses default file permissions
• MXS-3114 Listener creation via REST API with sockets doesn’t work

2.4.19

• MXS-3892 schema router flood information schemas with queries
• MXS-3885 MaxScale unconditionally loads global options from /etc/maxscale.cnf.d/maxscale.cnf
• MXS-3879 MaxScale doesn’t load maxscale section in persistent file after restart
• MXS-3873 Crash in qc_sqlite
• MXS-3617 writeq throttling can lose response packets
• MXS-3585 query classifier crashes after upgrade from 2.5.11 to 2.5.12
• MXS-3310 Amend documentation on keytab file location to mention the possibility to use the environment variable KRB5_KTNAME

2.5.15

• MXS-3719 Readwritesplit logs wrong warning when replication lag is not available
• MXS-3704 MaxScale always advertises the SESSION_TRACK capability even with servers that don’t support it (XPand)
• MXS-3703 Requirement to use cluster with xpandmon is not documented
• MXS-3698 “maxctrl classify” fails with an exception
• MXS-3695 Causal Consistency with MaxScale’s Read/Write Split Router issue
• MXS-3694 MXS – crash when cache is used with invalidate and hard_ttl
• MXS-3692 Improve host pattern error message
• MXS-3679 Mismatching user or source prevents session creation
• MXS-3674 Deadlock in binlogrouter
• MXS-3673 Draining servers is not documented
• MXS-3550 write statistic is incremented for slaves
• MXS-3532 Do not allow Galera master to be set to Drain
• MXS-3508 causal_reads=global results in missing data reads
• MXS-3478 admin_host missed on the static configuration parameters list
• MXS-3474 Strange persistent pool connection stats
• MXS-3299 Parse error when connecting (through binlog router) from mysql-connector-j

2.5.16

• MXS-3805 Binlogrouter error messages aren’t specific enough
• MXS-3804 Result size accounting is wrong
• MXS-3799 Destroyed monitors are not deleted
• MXS-3798 Race condition in service destruction
• MXS-3790 Fix luafilter
• MXS-3788 Debug assertion with default config and transaction_replay=true
• MXS-3779 binlogrouter logs warnings for ignored SQL
• MXS-3766 Not able to insert data on Masking enabled table
• MXS-3759 Client hangs forever when server failed or restarted
• MXS-3756 KILL behavior is not well documented
• MXS-3748 Crash when unified log cannot be created
• MXS-3747 Empty strings aren’t serialized as quoted strings
• MXS-3746 type=listener is added twice in listener serialization
• MXS-3738 maxctrl show dbusers does nothing
• MXS-3734 show binlog error msg is incorrect
• MXS-3728 Binlogrouter crashes when GTID is not found
• MXS-3718 MaxScale killed by watchdog timeout
• MXS-3657 CCR Filter ignores PCRE2 option ignorecase
• MXS-3580 Avrorouter should store full GTID coordinates
• MXS-3331 Could not bind connecting socket to local address
• MXS-3298 DNS server failure crashes Maxscale
• MXS-3254 Monitor failover fails
• MXS-3063 error : Sync marker mismatch.
• MXS-3060 Failed to load current GTID
• MXS-3050 Setting Up MaxScale documentation should include instructions on how to configure the MaxScale grants in ClustrixDB
• MXS-3049 error : [avrorouter] Reading Avro file failed with error ‘MAXAVRO_ERR_VALUE_OVERFLOW’.

2.5.17

• MXS-3885 MaxScale unconditionally loads global options from /etc/maxscale.cnf.d/maxscale.cnf
• MXS-3872 test_kafkacdc fails in 2.5
• MXS-3871 Kerberos tests are skipped in 2.5
• MXS-3870 The pam_authentication_2fa test fails very often
• MXS-3858 core dumps from system-tests (meta bug)
• MXS-3857 Pinloki initial gtid scan incorrectly reads entire files
• MXS-3856 Errors with causal_reads and read-only transactions
• MXS-3845 Sending binlog events is inefficient
• MXS-3832 Document privileges required for procs_priv system table
• MXS-3826 Allow maintenance mode to be set on Galera cluster master
• MXS-3824 Allow symbolic link for path to directory /usr/share/maxscale/gui
• 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-3815 maxscale crash
• MXS-3814 maxscale rpl_state is empty
• MXS-3810 SQL_MODE parsing sometimes fails
• 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-3801 Unexpected internal state with read-only cursor and result with one row
• MXS-3800 Not enough information in server state change messages
• MXS-3782 session_track_trx_state set to true causes incorrect routing of SELECT

2.5.18

• MXS-3938 Debug assert in xpandmon
• MXS-3934 Linking a service at runtime to an xpandmon doesn’t work
• MXS-3933 Avro reader client can fail
• MXS-3928 MaxScale logs a warning when users are loaded from a Xpand cluster
• MXS-3920 Can’t connect to MaxScale when schema uses utf8mb4 chars >= U0080
• MXS-3897 MaxScale crashes when executing CDC process to kafka

2.5.19

• 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-3949 “transaction” is always parsed as a reserved word
• MXS-3947 Read-only transaction behavior is not documented
• 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

2.5.20

• MXS-4110 Schemarouter does not ignore the sys schema
• MXS-4109 The /user/inet endpoint fails schema validation
• MXS-4103 Binlogrouter doesn’t decrypt passwords
• MXS-4096 Binlog Routers SHOW SLAVE STATUS does not show SSL information
• MXS-4093 User account manager does not detect db-level priv changes
• MXS-4092 schemarouter: duplicate tables found, if table differs on upper lower case only
• MXS-4086 REST API allows deletion of last user
• MXS-4074 Status of boostrap servers not always the same as the status of corresponding runtime servers
• MXS-4053 The cache does not handle multi-statements properly.
• MXS-4045 Add maxctrl command for dumping the whole REST API output
• MXS-4040 Mariadbmon constantly logs errors if event scheduler is disabled
• MXS-4039 Debug assert with connection_keepalive and slow server
• MXS-4038 maxctrl reload service does not bypass the users refresh rate limit
• MXS-4034 Persistent connection pool is not automatically flushed
• MXS-4024 CDC protocol logs a notice message for each new connection
• MXS-4023 Schema auto-generation is not documented
• MXS-4022 Avrorouter doesn’t log an error for failed SHOW CREATE TABLE
• MXS-4008 Query classifier cache does not properly record all used memory
• MXS-4004 Race condition in KILL command execution
• MXS-4003 GSSAPI authenticator documentation is out of date
• 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-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

2.5.21

• MXS-4194 Reported size for query classifier cache keeps growing
• MXS-4181 MaxScale w/SSL doesn’t work on FIPS RHEL7
• 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 Maxscale galeramon + max_slave_replication_lag = Could not find valid server for target type TARGET_SLAVE
• MXS-4152 Schemarouter performance degrades as the number of tables increases
• MXS-4151 Schemarouter duplicate checks are excessively slow
• MXS-4146 Xpand MaxScale Tutorial in KB doesn’t work
• MXS-4141 connection_keepalive=0 causes a memory leak
• 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-4132 router_options=master ignores rank for first server
• MXS-4127 MaxCtrl: list services does not include other targets
• MXS-4121 MaxCtrl is limited to 2GB of memory
• MXS-4120 Avrorouter crash with a SEQUENCE engine table
• MXS-4115 Maxscale prints user/pass with CHANGE MASTER command in logfile while failover.
• MXS-4110 Schemarouter does not ignore the sys schema
• MXS-4100 connection_keepalive=0 causes a memory leak

2.5.22

• MXS-4332 REST API reports unknown parameters with warnings and not errors
• MXS-4331 Altering servers fails if SSL is enabled
• 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-4304 MariaDB-Monitor spams log with connection errors if server is both [Maintenance] and [Down]
• MXS-4283 Race condition in KILL command processing
• MXS-4279 “sub” field not set for JWTs
• MXS-4269 UPDATE with user variable modification is treated as a session command
• 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-4227 MaxCtrl incompatibility with MemoryDenyWriteExecute=true is not documented
• MXS-4224 connection_timeout not documented to only take effect on the top level service
• 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-4156 Update documentation on required monitor privileges
• MXS-4148 Log warning if reverse name resolution takes significant time
• MXS-4094 Allow empty token when client is replying to AuthSwitchRequest

2.5.23

• MXS-4348 Full SASL support is not enabled for kafka modules
• MXS-4317 Smartrouter interrupts the wrong query

2.5.24

• 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-4423 Rebalancing is not always initiated from the affected worker/thread
• MXS-4404 Maxscale: KafkaCDC writes to current_gtid.txt causes high disk utilisation.

2.5.25

• 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-4548 The statement canonicalizer cannot handle comments within statements
• 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-4494 Replication breaks if binlogfilter excludes events
• MXS-4489 PHP program reports different collation_connection when connecting via Maxscale
• MXS-4476 Memory leak in smartrouter
• MXS-4474 MaxScale hangs with warning about “Worker 1 attempted to send a message to worker 1”
• MXS-4473 Hang in smartrouter under heavy load
• MXS-4469 Schemarouter routing logic documentation is out of date
• MXS-4459 Improve match/exclude documentation for avrorouter and kafkacdc
• MXS-4197 pinloki_start_stop is unstable
• MXS-3972 The rpl_state in binlogrouter is not atomic

2.5.26

• 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-4586 transaction_replay_max_size default is 1GiB instead of 1MiB
• MXS-4560 Not all passwords were obfuscated in the maxctrl report
• MXS-4550 Regular expression documentation is inaccurate and lacking
• MXS-4502 KB pages reference mysqlauth and mysqlauth is deprecated for mariadbauth

2.5.27

• MXS-4676 REST-API documentation is wrong about which server parameters can be modified
• MXS-4670 The fact that readconnroute doesn’t block writes with router_options=slave is not documented
• MXS-4665 Listener creation error is misleading
• MXS-4659 Cache filter hangs if statement consists of multiple packets.
• 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-4642 Document that the Xpand service-user requires “show databases” privilege
• MXS-4617 expire_log_duration not working

2.5.28

• 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-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-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-4664 xpandmon diagnostics are not useful
• MXS-4613 binlogrouter shows MaxScale’s binary log coordinates in SHOW SLAVE STATUS

2.5.29

• MXS-4807 MaxScale does not always report the OS version correctly
• MXS-4756 GUI caching issue
• 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-4724 slave_selection_criteria should accept lowercase version of the values
• MXS-4717 information_schema is not invalidated as needed
• MXS-4706 Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd

6.0.0

• 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

6.1.0

• 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.

6.1.1

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

6.1.2

• 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

6.1.3

• MXS-3796 maxscale 6.1.2 killed by SystemD watchdog

6.1.4

• 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

6.2.0

• 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

6.2.1

• 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

6.2.2

• 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

6.2.3

• 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

6.2.4

• 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

6.3.0

• 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

6.3.1

• 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

6.4.0

• 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

6.4.1

• 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

6.4.2

• 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”

6.4.3

• 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

6.4.4

• 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

6.4.5

• 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

6.4.6

• 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

6.4.7

• 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

6.4.8

• 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

6.4.9

• 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

6.4.10

• 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

6.4.11

• 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

6.4.12

• MXS-4847 Crash on maxctrl list sessions

6.4.13

• 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

6.4.14

• 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

6.4.15

• 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

22.08.0

22.08.1

• MXS-4274 maxctrl reload tls does not reload JWT signature keys
• MXS-4272 Certain NoSQL $rename operations can cause a crash
• MXS-4269 UPDATE with user variable modification is treated as a session command
• MXS-4260 Maxscale crashes frequently while performing load testing
• MXS-4250 A non-admin user cannot view its own information
• MXS-4249 When creating user, the NoSQL ‘userAdminAnyDatabase’ role is not handled properly
• 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-4231 Sometimes the date and time are missing in the query log
• MXS-4219 Settings of bootstrap servers are not correctly propagated to dynamic servers
• MXS-4196 Readconnroute load balancing behavior is not well documented
• MXS-4094 MaxScale failed to login mysql user with empty password

22.08.2

• MXS-4355 Token authentication does not work correctly with PAM users
• MXS-4353 /maxscale/logs/data endpoint doesn’t filter syslog contents correctly
• MXS-4350 The rebalancing functionality is claimed to be disabled
• MXS-4349 The documentation of the behaviour of ‘threads=auto’ in containers is incorrect
• MXS-4348 Full SASL support is not enabled for kafka modules
• MXS-4338 History/Snippets filter doesn’t work on the action and date columns
• MXS-4325 Listeners do not accept ssl_ca
• MXS-4321 Error from missing –secure option is not helpful
• MXS-4316 Data preview tab shows 2 execution time
• 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-4303 Disconnect connection in the reconnection dialog doesn’t work properly
• MXS-4299 Unsaved query tab isn’t saved when the current active query tab is not the one has unsaved changes
• MXS-4295 Switchover will wait even if slave server are lagging more than switchover_timeout
• MXS-4293 Memory leak with causal_reads=universal
• MXS-4292 Read-only transaction are not synchronized by causal_reads=universal
• MXS-4291 Avrorouter crash when client is closed
• 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-4281 Query editor connections aren’t bound to the query tabs properly
• MXS-4280 qc_sqlite does not properly handle a LIMIT clause
• MXS-4279 “sub” field not set for JWTs
• MXS-4278 The current connection name in the dropdown disappears when failed to connect to a new connection
• MXS-4253 Redirecting to 404 page after login with AD PAM user
• MXS-4251 Stop button is not working properly and high memory usage in the Query Editor
• MXS-4241 MaxScale High CPU / Load issue
• MXS-4174 expire_log_duration and expire_log_minimum_files not covered by tests
• MXS-4156 Update documentation on required monitor privileges
• MXS-4083 CPU utilization high on MaxScale host

22.08.3

• MXS-4421 Query classification data is unintentionally shared between multiple queries
• MXS-4418 use-after-free in regexfilter
• MXS-4416 Stalling connection after running some command
• MXS-4415 Warning for xpandmon for ‘leaving’ / ‘late, leaving’ being an unknown sub-state
• MXS-4413 UPDATE with user variable breaks replication
• MXS-4406 State Shown was Not Correct by ‘maxctrl list servers’ Command
• MXS-4404 Maxscale: KafkaCDC writes to current_gtid.txt causes high disk utilisation.
• MXS-4399 Query editor – Keyboard trap (accessibility)
• MXS-4397 fields parameter breaks REST-API filtering
• MXS-4393 Authentication failures during shard mapping are not handled correctly
• MXS-4392 Rebuild-server should read gtid from xtrabackup_binlog_info-file
• MXS-4389 Crash in handleError
• MXS-4388 LOAD DATA LOCAL INFILE and changing autocomit causing stuck
• MXS-4378 Obsolete “Run” button label
• MXS-4369 Save Script Is Not Working
• MXS-4365 Query tab is going infinite loop, unable to use the query tab after the infinite loop
• MXS-4360 New values on the GUI table aren’t updated until refresh the browser
• MXS-4358 Query editor doesn’t redirect to the login page after auth token is expired
• MXS-4356 Query classification sometimes treats table names as constants
• MXS-4352 Debug assertion when server deleted with persist_runtime_changes=false
• MXS-4347 error: no matching constructor for initialization of ‘maxsql::ComPacket’
• MXS-4317 Smartrouter interrupts the wrong query
• MXS-4301 Allow case-insensitive [maxscale] section name
• MXS-3043 Database grants in user_accounts_file should add the database to the list of known databases

22.08.4

• MXS-4476 Memory leak in smartrouter
• 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-4451 Memory issue in Maxscale
• MXS-4450 6.4 no longer provides full certificate chain in TLS HELLO
• MXS-4442 MaxScale crashes when a certificate chain is used with the REST-API
• MXS-4440 Lost connection to backend server: network error (server1: 104, Connection reset by peer)
• MXS-4435 Log rotation causes errors in qlafilter
• MXS-4434 SET STATEMENT variables are not ignored when statements are classified
• MXS-4427 TLS reloading leaks memory
• MXS-4423 Rebalancing is not always initiated from the affected worker/thread
• MXS-4197 pinloki_start_stop is unstable
• MXS-3972 The rpl_state in binlogrouter is not atomic

22.08.5

• MXS-4561 Some configuration cause no errors to be logged
• 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-4513 The connections graph the on GUI dashboard “jumps” on every refresh
• MXS-4512 Clang 15 compilation fails on 22.08
• 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-4488 MaxScale can hang if non-MariaDB data is sent to a MariaDB protocol port
• MXS-4481 Attempting to create a table with the name “DUAL” crashes MaxScale
• MXS-4461 Debug assertion in dcb.cc
• MXS-4459 Improve match/exclude documentation for avrorouter and kafkacdc
• MXS-4410 QLA filter not properly logging USE DBx command.

22.08.6

• MXS-4625 Query classifier does not classify XA transactions correctly.
• 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-4612 Query Editor: High memory usage when multiple statements are executed in a batch query
• 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-4571 Passwords appear masked even if they are not set
• MXS-4570 CREATE USER statements aren’t obfuscated in the Query Editor history query
• MXS-4569 Undefined behavior in simd_canonical.cc
• MXS-4560 Not all passwords were obfuscated in the maxctrl report
• 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

22.08.7

• MXS-4684 Detect ALTER EVENT failure on MariaDB 11.0
• MXS-4683 ssl parameters specified on the bootstrap server are not copied to the rest
• MXS-4680 Session idleness diagnostic is wrong
• MXS-4676 REST-API documentation is wrong about which server parameters can be modified
• MXS-4672 Document grants needed for MariaDB 11.1
• 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-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-4655 Missing kafkaimporter documentation
• 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
• MXS-4627 Rebalancing is unsafe to use with readwritesplit
• MXS-4613 binlogrouter shows MaxScale’s binary log coordinates in SHOW SLAVE STATUS

22.08.8

• MXS-4730 GUI default value of inputs in the object creation dialog is empty after closing the dialog
• MXS-4726 Session command response verification unnecessarily stores PS IDs for readconnroute
• 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-4717 information_schema is not invalidated as needed
• MXS-4714 qc_sqlite does not properly parse a RENAME statement
• MXS-4708 Update maxscale.cnf default file
• MXS-4706 Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd
• 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-4691 Binlogrouter cannot write binlog files larger than 4GiB
• MXS-4690 Binlogrouter runs out of memory on very large transactions
• MXS-4685 Replication via binlogrouter temporarily blocks the REST-API
• MXS-4681 Encrypted passwords are persisted in plaintext
• MXS-4677 MaxScale BinlogRouter skips large transactions causing data Inconsistency on attached slave
• MXS-4675 Switchover fails with ‘Unknown thread id’ error

22.08.9

• MXS-4831 Missing SQL error in server state change messages
• 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-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-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-4736 Read-only transaction sometimes loses statements with causal_reads=universal and transaction_replay=true
• MXS-4735 Connection IDs are missing from error messages
• MXS-4734 SET TRANSACTION READ ONLY is classified as a session command
• 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-4616 Limit the number of statements to be executed in the Query Editor
• 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

22.08.10

• MXS-4847 Crash on maxctrl list sessions
• MXS-4803 Binlog encryption broken

22.08.11

• MXS-4881 Startup option –basedir mishandled
• MXS-4869 Parameter table isn’t refreshed after update in the GUI
• MXS-4856 GUI failed to create a monitor in a monitored server detail page
• MXS-4851 No space or separator between 2 routing targets in the services dashboard
• MXS-4798 Broken slave promoted to master when no other servers are available

22.08.12

• 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-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-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-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-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-4943 delayed_retry timeout errors do not have enough information
• 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-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-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-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-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

22.08.13

• 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-5068 users_refresh_time=0s does not work as documented
• 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-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-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

22.08.14

• MXS-5234 webpack warns about yargs
• 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-5210 Text could be selected during server node drag for switch-over
• 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-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-5162 Post reboot binlog router entered stuck state
• MXS-5160 postinst script prints output while installing
• MXS-5154 Adding or removing objects resets the GUI configuration graph’s zoom ratio
• 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
• MXS-4605 Monitor should drop the connection when faced with an Access Denied error

22.08.15

• 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-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-5359 Transaction replay may deadlock with switchover
• MXS-5357 Improve MariaDB Monitor documentation on auto_failover and auto_rejoin
• 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-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-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-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-5243 The No Backslash Escapes checkbox in the result export dialog is confusing
• 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

22.08.16

• MXS-5536 Early mismatched responses to session commands do not close connections
• 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-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-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-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-5429 Resultset is not selected automatically with Inactive query tabs
• 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-5403 Debug assertion on very large binary protocol prepared statements
• 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-5314 Resultset table not fully expanded for inactive query tab

22.08.17

• 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

23.02.0

• MXS-4490 Query Editor – A query tab becomes unusable when a connection is not successfully reconnected.

23.02.1

• 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-4410 QLA filter not properly logging USE DBx command.

23.02.2

• MXS-4625 Query classifier does not classify XA transactions correctly.
• 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-4612 Query Editor: High memory usage when multiple statements are executed in a batch query
• MXS-4611 Readwritesplit prefers idle primary over busy replicas
• MXS-4602 Qlafilter logs responses from non-matched queries
• MXS-4601 Query Editor doesn’t quote identifier names properly
• 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-4571 Passwords appear masked even if they are not set
• MXS-4569 Undefined behavior in simd_canonical.cc
• MXS-4564 I/O activity status missed on the Server current sessions
• MXS-4561 Some configuration cause no errors to be logged
• MXS-4560 Not all passwords were obfuscated in the maxctrl report
• MXS-4557 Binlogrouter breaks if event size exceeds INT_MAX
• MXS-4556 Maxscale ignores lower_case_table_names=1 on config file
• 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

23.02.3

• MXS-4684 Detect ALTER EVENT failure on MariaDB 11.0
• MXS-4683 ssl parameters specified on the bootstrap server are not copied to the rest
• MXS-4681 Encrypted passwords are persisted in plaintext
• MXS-4680 Session idleness diagnostic is wrong
• MXS-4676 REST-API documentation is wrong about which server parameters can be modified
• MXS-4672 Document grants needed for MariaDB 11.1
• 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-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-4655 Missing kafkaimporter documentation
• 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 Manually deleting log files breaks the file purge (expiration).
• MXS-4628 Connection in Query Editor is closed after 1 hour of being idle
• MXS-4613 binlogrouter shows MaxScale’s binary log coordinates in SHOW SLAVE STATUS

23.02.4

• MXS-4730 GUI default value of inputs in the object creation dialog is empty after closing the dialog
• MXS-4726 Session command response verification unnecessarily stores PS IDs for readconnroute
• 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-4717 information_schema is not invalidated as needed
• MXS-4714 qc_sqlite does not properly parse a RENAME statement
• MXS-4708 Update maxscale.cnf default file
• MXS-4706 Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd
• 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-4694 Update MaxGUI screenshots in the documentation
• MXS-4691 Binlogrouter cannot write binlog files larger than 4GiB
• MXS-4690 Binlogrouter runs out of memory on very large transactions
• MXS-4685 Replication via binlogrouter temporarily blocks the REST-API
• MXS-4677 MaxScale BinlogRouter skips large transactions causing data Inconsistency on attached slave
• MXS-4675 Switchover fails with ‘Unknown thread id’ error
• MXS-4674 Crash in mxs1687_avro_ha
• MXS-4668 Binlogrouter eventually stops working if semi-sync replication is not used

23.02.5

• MXS-4831 Missing SQL error in server state change messages
• 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-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-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-4768 Empty objects for selecting in “Objects Selection” stage of Data migration
• MXS-4767 Rebuild-server and related operations fail with “No route to host”
• MXS-4766 maxctrl create report cannot write to a pipe
• MXS-4765 Serialization of regular expressions doesn’t add escaping slashes
• MXS-4763 Logs viewer in data migration worksheet doesn’t automatically scroll to the bottom
• 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-4736 Read-only transaction sometimes loses statements with causal_reads=universal and transaction_replay=true
• MXS-4735 Connection IDs are missing from error messages
• MXS-4734 SET TRANSACTION READ ONLY is classified as a session command
• MXS-4732 MaxScale shutdown is not signal-safe
• MXS-4724 slave_selection_criteria should accept lowercase version of the values
• MXS-4718 Add replication_custom_options to enable replication TLS certification check
• MXS-4707 The match parameters are not regular expressions
• MXS-4686 Undefined behavior in ed25519 plugin
• 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

23.02.7

• MXS-4881 Startup option –basedir mishandled
• MXS-4869 Parameter table isn’t refreshed after update in the GUI
• MXS-4856 GUI failed to create a monitor in a monitored server detail page
• MXS-4851 No space or separator between 2 routing targets in the services dashboard
• MXS-4798 Broken slave promoted to master when no other servers are available

23.02.8

23.02.9

• MXS-5007 Top-level service reconnection may cause a use-after-free
• 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-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-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-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-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-4920 GUI Logs Archive has infinite loading indicator when fetching older logs
• 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-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-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

23.02.10

• MXS-5107 ‘Connection Busy’ error causes empty schema tree explorer
• MXS-5095 Master Stickiness state is not documented
• 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-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-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

23.02.11

• MXS-5234 webpack warns about yargs
• 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-5197 Failed to drop the trigger due to invalid syntax in the Query Editor
• 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-5162 Post reboot binlog router entered stuck state
• 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-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

23.02.12

• 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-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-5359 Transaction replay may deadlock with switchover
• MXS-5357 Improve MariaDB Monitor documentation on auto_failover and auto_rejoin
• 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-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

23.02.13

• MXS-5536 Early mismatched responses to session commands do not close connections
• 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-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-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-5409 list session in GUI shows wrong amount of sessions
• MXS-5408 rebuild-server does not work with MariaDB 11.4
• MXS-5403 Debug assertion on very large binary protocol prepared statements
• 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

23.02.14

• 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

23.08.0

23.08.1

• 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

23.08.2

• 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

23.08.3

• 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

23.08.4

• 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

23.08.5

• 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

23.08.6

• 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

23.08.7

• 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

23.08.8

• 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

23.08.9

• 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

23.08.10

• 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

24.02.0

24.02.1

• 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

24.02.2

• MXS-5106 Server version checks are overly pessimistic
• MXS-5104 Connection busy error occurs when connecting to a listener in the Query Editor
• 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-5039 cooperative_monitoring_locks can leave stale locks on a server if network breaks
• MXS-5038 Maxscale key limitations
• 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-4964 Simple sharding tutorial is out of date
• MXS-4902 MariaDB Monitor command reset-replication can be started on a secondary MaxScale

24.02.3

• 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-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-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-5179 Active schema is not highlighted in the schema tree explorer
• MXS-5171 MaxScale does not have time to open the file during rotation for a new binlog
• MXS-5165 MariaDB Monitor rebuild server may try to chown “/var/lib/mysql/” instead of just “/var/lib/mysql”
• MXS-5162 Post reboot binlog router entered stuck state
• 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-5129 Cache may delete values from LRU but not from storage
• MXS-5128 Failed patching passive parameter value
• 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

24.02.4

• 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-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-5384 maxscale version 24 auth_all_servers not picking up users on replicas
• 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-5366 Certain special characters in the maxscale user causes async-rebuild-server to fail
• 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-5269 Unexpected response after failed session command
• 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-5218 Binlgorouter purge
• MXS-5178 Replicas after maxscale binlog don’t get updates
• MXS-4933 Using targets=... in maxctrl create service should be allowed

24.02.5

• MXS-5533 Remove session_trace parameter from services section
• 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-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-5519 Documentation regarding mixing of cooperative_monitoring_locks and passive is unclear
• MXS-5518 Documentation of switchover-force lacks warnings
• MXS-5516 gtid_start_pos=newest is not documented for avrorouter
• 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-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-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-5471 GUI reference doc links are broken
• MXS-5466 MaxCtrl warnings are very verbose
• 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-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-5438 Galeramon doesn’t update GTID positions internally
• 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-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-5365 Binlogrouter cannot open compressed files
• MXS-5340 ed25519 socket droped when no user_mapping_file
• MXS-5314 Resultset table not fully expanded for inactive query tab

24.02.6

• 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-5564 Query Editor default connection type preference is changed unexpectedly
• 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-5544 Prepared statements fail through schemarouter for Columnstore
• MXS-5525 Masking with functions uses wrong rule settings

【免責事項】

• 本ページは株式会社スマートスタイル（以下、当社）が、情報提供を目的として提供しているものです。
• 当社は本ページで提供される内容に関し、その正確性、有用性、確実性その他いかなる保証も致しかねます。
• 本ページの著作権は、提供元の企業に帰属します。
• 許諾なく無断で改変、公衆配信、販売、出版、翻訳／翻案することは営利目的、非営利目的に関わらず禁じられています。