hcq/MaxScale
hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch '2.4.0' into 2.4

Browse Source
This commit is contained in:
Johan Wikman 2019-06-25 11:48:44 +03:00
commit 28a2a726f8
15 changed files with 1 additions and 1090 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
Documentation/Release-Notes/MaxScale-2.2.17-Release-Notes.md
View File

@ -1,38 +0,0 @@
# MariaDB MaxScale 2.2.17 Release Notes -- 2018-11-28
Release 2.2.17 is a GA release.
This document describes the changes in release 2.2.17, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2175](https://jira.mariadb.org/browse/MXS-2175) available_when_donor=true is not respected in Galera Monitor with xtrabackup-v2 sst method and only one synced node available in the cluster
* [MXS-2159](https://jira.mariadb.org/browse/MXS-2159) Oracle Connector/J 8.0 with SSL doesn't work with MaxScale
* [MXS-2151](https://jira.mariadb.org/browse/MXS-2151) MaxScale does not log any info when "Connection killed by MaxScale: Router could not recover from connection errors"
* [MXS-2106](https://jira.mariadb.org/browse/MXS-2106) Maxscale CDC JSON output does not respect null values
* [MXS-2095](https://jira.mariadb.org/browse/MXS-2095) Fatal: MaxScale 2.2.15 received fatal signal 11 - libavrorouter.so(count_columns+0x21)
* [MXS-2081](https://jira.mariadb.org/browse/MXS-2081) Unable to execute maxctrl commands in RHEL 6 - Maxscale 2.2.9
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

37
Documentation/Release-Notes/MaxScale-2.2.18-Release-Notes.md
View File

@ -1,37 +0,0 @@
# MariaDB MaxScale 2.2.18 Release Notes -- 2018-12-13
Release 2.2.18 is a GA release.
This document describes the changes in release 2.2.18, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2221](https://jira.mariadb.org/browse/MXS-2221) Fatal signal handling does not always create a core
* [MXS-2216](https://jira.mariadb.org/browse/MXS-2216) Read past stack buffer
* [MXS-2213](https://jira.mariadb.org/browse/MXS-2213) Growing memory consumption with 2.2.17
* [MXS-2207](https://jira.mariadb.org/browse/MXS-2207) qc_mysqlembedded does not classify SET STATEMENT ... FOR UPDATE correctly.
* [MXS-2183](https://jira.mariadb.org/browse/MXS-2183) Excessive memory use, but not growing endlessly
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

39
Documentation/Release-Notes/MaxScale-2.2.19-Release-Notes.md
View File

@ -1,39 +0,0 @@
# MariaDB MaxScale 2.2.19 Release Notes -- 2019-01-11
Release 2.2.19 is a GA release.
This document describes the changes in release 2.2.19, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2248](https://jira.mariadb.org/browse/MXS-2248) INSERT sent to all nodes
* [MXS-2242](https://jira.mariadb.org/browse/MXS-2242) MaxScale does not recognize builtin read-only functions
* [MXS-2238](https://jira.mariadb.org/browse/MXS-2238) MaxScale fails to send large CDC schemas
* [MXS-2234](https://jira.mariadb.org/browse/MXS-2234) Add extra info to log when MaxScale loads persisted configuration files
* [MXS-2232](https://jira.mariadb.org/browse/MXS-2232) version_string prefix 5.5.5- is always added
* [MXS-2231](https://jira.mariadb.org/browse/MXS-2231) Kerberos together with ssl doesn't work
* [MXS-2048](https://jira.mariadb.org/browse/MXS-2048) Rewrite dbfwfilter module command documentation
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

40
Documentation/Release-Notes/MaxScale-2.2.20-Release-Notes.md
View File

@ -1,40 +0,0 @@
# MariaDB MaxScale 2.2.20 Release Notes -- 2019-03-15
Release 2.2.20 is a GA release.
This document describes the changes in release 2.2.20, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2375](https://jira.mariadb.org/browse/MXS-2375) maxctrl stop maxscale is confusing
* [MXS-2368](https://jira.mariadb.org/browse/MXS-2368) maxctrl requires password on command line and cannot change user password
* [MXS-2335](https://jira.mariadb.org/browse/MXS-2335) lower_case_table_names doesn't work
* [MXS-2322](https://jira.mariadb.org/browse/MXS-2322) Null characters in passwords break maxctrl
* [MXS-2311](https://jira.mariadb.org/browse/MXS-2311) connection_keepalive and error : (4852) Unexpected internal state: received response 0x00 from server
* [MXS-2296](https://jira.mariadb.org/browse/MXS-2296) maxscale-system-test does not generate core dumps
* [MXS-2268](https://jira.mariadb.org/browse/MXS-2268) readwritesplitter is not routing queries properly in Maxscale 2.3.2
* [MXS-2206](https://jira.mariadb.org/browse/MXS-2206) Cmake version check fails with version = 3.10.2
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

41
Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md
View File

@ -1,41 +0,0 @@
# MariaDB MaxScale 2.2.21 Release Notes -- 2019-05-08
Release 2.2.21 is a GA release.
This document describes the changes in release 2.2.21, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2410](https://jira.mariadb.org/browse/MXS-2410) Hangup delivered to wrong DCB
* [MXS-2366](https://jira.mariadb.org/browse/MXS-2366) Wrong tarball RPATH
## Changes to MariaDB-Monitor failover
Failover is no longer disabled permanently if it or any other cluster operation fails.
The disabling is now only temporary and lasts for 'failcount' monitor iterations. Check
[MariaDB-Monitor documentation](../Monitors/MariaDB-Monitor.md#limitations-and-requirements)
for more information.
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

369
Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
View File

@ -1,369 +0,0 @@
# MariaDB MaxScale 2.3.0 Release Notes -- 2018-10-09
Release 2.3.0 is a Beta release.
This document describes the changes in release 2.3.0, when compared to
release 2.2.
For any problems you encounter, please consider submitting a bug
report at [Jira](https://jira.mariadb.org).
## Changed Features
### maxadmin `list threads`
Maxadmin `list threads` now shows the descriptor counts and load of
the MaxScale worker threads. For details, please consult the
maxadmin [documentation](../Reference/MaxAdmin.md).
### MaxCtrl `create monitor`
The `create monitor` command now accepts a list of key-value parameters that are
passed to the monitor as the last argument. This allows creation and
configuration of monitors in one command.
### `query_retries`
The default value of `query_retries` was changed from 0 to 1. This turns
on failure tolerant queries for monitors and authenticators which prevents
failures due to network problems. A single reconnection attempt is made to
keep responsiveness high even with default values.
### Session Command History
The _readwritesplit_ session command history is now enabled by default but it
is limited to a total of 50 distict session commands. This default allows most
sessions to leverage the newly improved reconnection mechanism without having to
explicitly enable the history. When the limit of 50 commands is exceeded, the
session command history is disabled. This makes it possible to use pooled
connections by default without having to explicitly disable the history (this
was the case with pre-2.1 versions of MaxScale).
The way that the history is stored has also changed. Instead of storing all
session commands, each session only stores the first and last execution of each
command. This way the history is compressed into a compact representation while
still retaining the relative order of each command.
To keep the old functionality, add `disable_sescmd_history=true` to the service
definition.
### Cache Filter
The rules can now be expressed using a JSON array containing rule objects,
which makes it easier to express more complex rules. Please see the
[Cache](../Filters/Cache.md) documentation for details.
### Masking Filter
By default the masking filter rejects statements that use functions on
conjuction with columns that should be masked. Please see the
[Masking Filter](../Filters/Masking.md) documentation for details.
### `router_options` in Binlogrouter
The use of `router_options` with the binlogrouter module is deprecated in
MaxScale 2.3 and will be removed in a subsequent release. The
`router_options` should be converted into separate parameters.
### `thread_stack_size`
The `thread_stack_size` configuration parameter is ignored and has been
deprecated. If you need to explicitly set the stack size, do so using
`ulimit -s` before starting MaxScale.
### `ssl` for Servers and Listeners
The `ssl` parameter now accepts boolean values ìn addition to the old `required`
and `disabled` values.
### MariaDBMonitor
MariaDBMonitor has undergone several changes listed briefly below. Please see
[MariaDBMonitor documentation](../Monitors/MariaDB-Monitor.md) for more details.
#### JSON diagnostics output changed
The data in the diagnostic output of the REST-API has changed, with some fields
removed and others added.
#### Master detection
The monitor is now less likely to suddenly change the master server, even if
another server has more slaves than the current master. The DBA can force a
master reselection by setting the current master read-only, or by removing all
its slaves if the master is down.
Only one server can have the *Master* status flag at a time, even in a
multimaster setup. Others servers in the multimaster group are given the *Relay
Master* and *Slave* status flags.
#### Switchover new master autoselection
The switchover command can now be called with just the monitor instance name as
parameter. In this case the monitor will automatically select a server for
promotion.
#### Replication lag detection
The replication lag measurement now simply reads the
*Seconds_Behind_Master*-field of the slave status output of slaves. The slave
calculates this value by comparing the time stamp in the binlog event the slave
is currently processing to the slave's own clock. If a slave has multiple slave
connections, the smallest lag is used.
#### Low disk space detection, automatic switchover
With recent MariaDB Server versions, the monitor can check the disk space on the
backends and detect if the server is running low. The monitor can be set to
automatically switchover a master low on disk space. Slaves can be set to
maintenance mode. Disk space is also considered when selecting a new master for
promotion. See
[switchover_on_low_disk_space](../Monitors/MariaDB-Monitor.md#switchover_on_low_disk_space)
and
[maintenance_on_low_disk_space](../Monitors/MariaDB-Monitor.md#maintenance_on_low_disk_space)
for more information.
#### Replication reset feature
The *reset-replication* monitor command deletes all slave connections and binary
logs, and then sets up replication. Useful when data is in sync but gtid:s are
not.
#### Scheduled events handling in failover/switchover/rejoin
Server events lauched by the event scheduler thread are now handled during
cluster modification operations. See
[handle_server_events](../Monitors/MariaDB-Monitor.md#handle_server_events)
for more information.
#### Unused parameters
The following parameters are unused and are ignored if set:
- `mysql51_replication` MySQL5.1 is no longer supported.
- `multimaster` The monitor now always detects multimaster setups.
- `allow_cluster_recovery` Now always on.
- `detect_replication_lag` Lag detection no longer writes to databases so it is
always on.
## Dropped Features
### `log_to_shm` parameter and `--log=shm` option
The following commands no longer create the log files in shared memory and will
be ignored. MaxScale will behave as if `--log=file` was provided when
`--log=shm` is used. The `log_to_shm` parameter is ignored. Both the parameter
and the optino value are deprecated and will be removed in a later relesae.
Logs can still be created in shared memory by pointing `logdir` to `/dev/shm`.
### Configuration Reloading
The deprecated `maxadmin reload config` command has been removed.
### `router_options` in Avrorouter
The use of `router_options` with avrorouter was deprecated in MaxScale 2.1. In
MaxScale 2.3, the use of `router_options` is no longer supported and the options
should be given as parameters instead.
### `router_options` in readwritesplit
The use of `router_options` with readwritesplit, which was deprecated in
MaxScale 2.2.0, has been removed in MaxScale 2.3.0.
### `QUERY-LAST-TRANSACTION` and `QUERY-TRANSACTION` CDC commands
The CDC protocol no longer accepts the `QUERY-LAST-TRANSACTION` and
`QUERY-TRANSACTION` commands. They were removed due to the addition of the REST
API that provides the same information in a more easy to process format.
## New Features
### Binlog Router
If the binlog router is replicating from a Galera cluster it is now
possible to specify secondary masters that the binlog router automatically
will switch to, in case the primary master for some reason goes down.
Please see the binlog router
[documentation](../Routers/Binlogrouter.md)
for details.
### Hints
There is now a new hint `last` that will cause a query to be routed to the
same server the previous query was routed to.
### Backend Connection IDs
The backend connection IDs are now shown in the `show sessions` output of
MaxCtrl.
### Comment Filter
With the comment filter it is possible to prepend statement received
with a comment before it is sent further to a server. Please see the
[comment filter documentation](../Filters/Comment.md)
for more details.
### Query Classifier Cache
The query classifier now caches the results of each classification which
significantly improves performance of workloads that require query
classification. The default cache size limit is 40% of total system memory.
Read [the configuration guide](../Getting-Started/Configuration-Guide.md#query_classifier_cache_size)
for more information about the details of the query classifier cache and how to
configure it.
### Runtime Configuration of the Cache
With the variables `@maxscale.cache.use` and `@maxscale.cache.populate`
it is now possible for a client to specify whether the cache should be
used and/or populated. Please see the
[Cache](../Filters/Cache.md) documentation for details.
### User Specified Syslog Facility and Level for Authentication Errors
It is now possible for the end user to specify the syslog facility and level
for authentication errors. Please see
[the configuration guide](../Getting-Started/Configuration-Guide.md#events)
for details.
### Named Server Filter
The `source` parameter can now contain a list of comma separated addresses.
### Table Family Sharding
The SchemaRouter is now capable of table family sharding. Please see the
SchemaRouter [documentation](../Routers/SchemaRouter.md) for details.
### Throttle filter
The [throttlefilter](../Filters/Throttle.md) replaces and extends on the limit_queries
functionality of [the Database Firewall filter](../Filters/Database-Firewall-Filter.md).
### ReadWriteSplit
A set of new features have been added to readwritesplit.
#### `transaction_replay`
The [`transaction_replay`](../Routers/ReadWriteSplit.md#transaction_replay)
parameter enables replaying of transactions if a master server is lost
mid-transaction. This allows transparent replacement of master servers with a
minimal amount of failed transactions.
#### `master_reconnection`
With the
[`master_reconnection`](../Routers/ReadWriteSplit.md#master_reconnection)
parameter, if the connection to a master server is lost or the master server
changes, readwritesplit can now reconnect seamlessly to the master server
without losing the session state.
#### `delayed_retry`
The [`delayed_retry`](../Routers/ReadWriteSplit.md#delayed_retry) parameter
allows queries to be automatically retried if their execution is interrupted.
#### `causal_reads`
The [`causal_reads`](../Routers/ReadWriteSplit.md#causal_reads) parameter
enables distributed consistent reads with MariaDB version 10.2 and newer.
#### `optimistic_trx`
The [`optimistic_trx`](../Routers/ReadWriteSplit.md#optimistic_trx) parameter
enables optimistic transaction execution. This parameter controls whether normal
transactions (i.e. `START TRANSACTION` or `BEGIN`) are load balanced across
slaves. If the transaction tries to modify a row, it is migrated to the master
and rolled back on the slave.
#### Adaptive Routing
A new load balancing method,
[`ADAPTIVE_ROUTING`](../Routers/ReadWriteSplit.md#slave_selection_criteria), was
added. It uses the average query response time to distribute the load so that it
is optimal on all servers.
### MaxCtrl
For more detailed information about the features of MaxCtrl, see the
[documentation](../Reference/MaxCtrl.md) or the output of `maxctrl help`.
#### Interactive Mode for MaxCtrl
MaxCtrl can now be started in an interactive mode similar to MaxAdmin. This
makes use of passwords more convenient as they have to be input only once and
they are cached for the duration of the session.
#### Draining Server Connections
The new `drain server` drains the server of connections by first removing it
from all services after which it waits until all connections are closed. When
all connections are closed, the server is put into the `maintenance` state and
added back to all the services where it was removed from.
### Resultset Concatenation Router
A new experimental router module, `cat`, was added to the
`maxscale-experimental` package. The `cat` router is a special router that
concatenates result sets. For more information and an explanation on how the
router works, read the [`cat` documentation](../Routers/Cat.md).
### REST API Additions
#### Creation of Services and Filters at Runtime
The REST API and MaxCtrl now support the creation and destruction of services
and filters at runtime. This also means that the filters of a service can now be
modified at runtime. Refer to the [REST API](../REST-API/API.md) and
[MaxCtrl](../Reference/MaxCtrl.md) documentation for more details.
#### Alteration of Routers
The router parameters of services can now be altered at runtime. Currently only
the readwritesplit router implements this feature.
### Binlog Filtering
The `binlogfilter` is a filter module that allows the client side stream of
binlogs to be filtered. It is designed to be used with the binlogrouter.
This allows conditional replication similar to _replicate_do_table_ but with
full PCRE2 compliant match/exclude functionality. For more information, refer to
the [binlogfilter](../Filters/BinlogFilter.md) documentation.
### Network Traffic Buffering
The new
[`writeq_high_water`](../Getting-Started/Configuration-Guide.md#writeq_high_water)
and
[`writeq_low_water`](../Getting-Started/Configuration-Guide.md#writeq_low_water)
parameters allow network traffic to be throttled if it exceeds the highwater
mark. This can be used to prevent MaxScale from buffering too much data in
memory if the client is not reading results fast enough.
## Bug fixes
[Here is a list of bugs fixed in MaxScale 2.3.0.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.3.0)
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for the Linux distributions supported
by MariaDB Enterprise.
Packages can be downloaded [here](https://mariadb.com/resources/downloads).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is X.Y.Z. Further, *master* always refers to the latest released non-beta version.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

153
Documentation/Release-Notes/MaxScale-2.3.1-Release-Notes.md
View File

@ -1,153 +0,0 @@
# MariaDB MaxScale 2.3.1 Release Notes -- 2018-11-20
Release 2.3.1 is a Beta release.
This document describes the changes in release 2.3.1, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Changed Features
### Unknown global parameters
Unknown global parameters or parameters with invalid values are now treated as
errors. If MaxScale refuses to start after upgrading to 2.3.1, check whether it
is due to an unknown global parameter.
### REST-API
#### `/v1/sessions`
The response will, if the feature has been enabled with the
`retain_last_statements` parameter, either globally or specifically
for a service, contain information about the last queries executed
by a session.
### Binlog Router
Secondary masters can now be specified also when file + position
based replication is used. Earlier it was possible only in conjunction
with GTID based replication.
### `mmmon` and `ndbclustermon`
Both of these modules have been deprecated and will be removed in a future
release. The functionality in `mmmon` has been largely obsoleted by the
advancements in `mariadbmon`. The `ndbclustermon` is largely obsolete due to the
fact that there are virtually no users who use it.
## Deprecated features
The following configuration file options have been deprecated and will
be removed in 2.4.
#### Global section
* `non_blocking_polls`, ignored.
* `poll_sleep`, ignored.
* `thread_stack_size`, ignored.
#### Services and Monitors
* `passwd`, replaced with `password`.
### MaxAdmin
MaxAdmin has been deprecated in favor of the REST API and MaxCtrl. It will be
removed in a later release.
In addition to this the commands `set pollsleep` and `set nbpolls` have been
deprecated and will be removed already in 2.4.
### MaxInfo
The `maxinfo` router has been deprecated and will be removed in a later release.
### Debugcli
The `debugcli` module has been deprecated and will be removed in 2.4.
## New Features
### ColumnStore Monitor
The new `csmon` monitor can be used to monitor ColumnStore clusters where the
primary UM will be assigned as the master and secondary UMs as slaves. Automatic
detection of the primary UM is supported with ColumnStore versions 1.2.1 and
newer. For older versions the primary UM must be designated with the `primary`
parameter of the monitor.
Read the [csmon documentation](../Monitors/ColumnStore-Monitor.md) for more
information on how to use it.
### MaxCtrl
There is now a new command `classify <statement>` using which it can
be checked if and how MaxScale classifies a specific statement. This
feature can be used for debugging, if there is suspicion that MaxScale
sends a particular statement to the wrong server (e.g. to a slave when it
should be sent to the master).
### Services
The global configuration parameter `retain_last_statements` can now
also be specified separately for individual services.
### Watchdog
If MaxScale is running as a systemd service, the systemd Watchdog can be
enabled and MaxScale will behave accordingly. Please see the
[documentation](../Getting-Started/Configuration-Guide.md#systemd-watchdog)
for more details.
By default the watchdog is disabled.
*NOTE*: In 2.3.1 there is a deficiency that manifests itself so that if
_any_ administrative operation, performed using _maxctrl_ or _maxadmin_,
takes longer that the specified watchdog timeout, then the watchdog will
kill and restart MaxScale. Please take that into account before enabling
the watchdog.
### Miscellaneous
* [MXS-2141](https://jira.mariadb.org/browse/MXS-2141) Retry read on master when causal_reads timeout is exceeded
* [MXS-2122](https://jira.mariadb.org/browse/MXS-2122) Immediately close the listening socket when a listener is destroyed
* [MXS-2077](https://jira.mariadb.org/browse/MXS-2077) Provide more information in list clients output.
* [MXS-1976](https://jira.mariadb.org/browse/MXS-1976) MaxAdmin Shutting Down A Service should specify / warn that new session requests are neither accepted nor denied.
## Bug fixes
* [MXS-2147](https://jira.mariadb.org/browse/MXS-2147) Luafilter is missing symbols
* [MXS-2144](https://jira.mariadb.org/browse/MXS-2144) Doing a controlled shutdown doesn't trigger query retrying
* [MXS-2142](https://jira.mariadb.org/browse/MXS-2142) Default timeout value for causal_reads is excessive
* [MXS-2140](https://jira.mariadb.org/browse/MXS-2140) Enabling transaction_replay at runtime doesn't enable implicit parameters
* [MXS-2139](https://jira.mariadb.org/browse/MXS-2139) transaction_replay doesn't implicitly enable master_failure_mode=fail_on_write
* [MXS-2136](https://jira.mariadb.org/browse/MXS-2136) passwd errors out as a attribute in [monitor] and [service] in maxscale.cnf
* [MXS-2121](https://jira.mariadb.org/browse/MXS-2121) Listeners defined in the configuration cannot be destroyed
* [MXS-2109](https://jira.mariadb.org/browse/MXS-2109) query_classifier_cache_size is per thread
* [MXS-2107](https://jira.mariadb.org/browse/MXS-2107) writeq_high_water doesn't work
* [MXS-2100](https://jira.mariadb.org/browse/MXS-2100) Unknown global parameters are not detected
* [MXS-2098](https://jira.mariadb.org/browse/MXS-2098) maintenance_on_low_disk_space does not work
* [MXS-2096](https://jira.mariadb.org/browse/MXS-2096) SELECT ... INTO OUTFILE is routed to all back end servers
* [MXS-2055](https://jira.mariadb.org/browse/MXS-2055) Monitor REST-API documentation
* [MXS-1978](https://jira.mariadb.org/browse/MXS-1978) SELECT INTO OUTFILE is routed to all servers
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

70
Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md
View File

@ -1,70 +0,0 @@
# MariaDB MaxScale 2.3.2 Release Notes -- 2018-12-03
Release 2.3.2 is a GA release.
This document describes the changes in release 2.3.2, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Changed Features
### Watchdog
The systemd watchdog is now safe to use in all circumstances.
By default it is enabled with a timeout of 60 seconds.
### Readwritesplit
#### `connection_keepalive`
The default value of `connection_keepalive` is now 300 seconds. This prevents
the connections from dying due to wait_timeout with longer sessions. This is
especially helpful with pooled connections that stay alive for a very long time.
### MariaDBMonitor
The monitor by default assumes that hostnames used by MaxScale to connect to the backends
are equal to the ones backends use to connect to each other. Specifically, for the slave
connections to be properly detected the `Master_Host` and `Master_Port` fields of the
output to "SHOW ALL SLAVES STATUS"-query must match server entries in the MaxScale
configuration file. If the network configuration is such that this is not the case, the
setting `assume_unique_hostnames` should be disabled.
## New Features
* [MXS-1598](https://jira.mariadb.org/browse/MXS-1598) heartbeat replication don't support multimaster
## Bug fixes
* [MXS-2189](https://jira.mariadb.org/browse/MXS-2189) optimistic_trx is rolled back if master fails
* [MXS-2188](https://jira.mariadb.org/browse/MXS-2188) MaxScale crashing when replicating
* [MXS-2187](https://jira.mariadb.org/browse/MXS-2187) Transaction replay is only attempted once
* [MXS-2186](https://jira.mariadb.org/browse/MXS-2186) SHOW DATABASES is routed to the master
* [MXS-2184](https://jira.mariadb.org/browse/MXS-2184) event_number is not incremented for updates
* [MXS-2179](https://jira.mariadb.org/browse/MXS-2179) Watchdog notifications must be generated also when users are fetched.
* [MXS-2178](https://jira.mariadb.org/browse/MXS-2178) Admin operations may cause systemd watchdog to be triggered.
* [MXS-2167](https://jira.mariadb.org/browse/MXS-2167) Monitors should be able to use extra_port
* [MXS-2158](https://jira.mariadb.org/browse/MXS-2158) Node rejoin fails, if the node was never a slave (but was master before going down)
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

44
Documentation/Release-Notes/MaxScale-2.3.3-Release-Notes.md
View File

@ -1,44 +0,0 @@
# MariaDB MaxScale 2.3.3 Release Notes -- 2019-01-21
Release 2.3.3 is a GA release.
This document describes the changes in release 2.3.3, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2266](https://jira.mariadb.org/browse/MXS-2266) COM_STMT_CLOSE causes a warning to be logged
* [MXS-2259](https://jira.mariadb.org/browse/MXS-2259) Maxscale consumes large amounts of memory even with buffer limits set.
* [MXS-2258](https://jira.mariadb.org/browse/MXS-2258) GaleraMon crashes if it monitors a server that is not Galera-enabled
* [MXS-2248](https://jira.mariadb.org/browse/MXS-2248) INSERT sent to all nodes
* [MXS-2242](https://jira.mariadb.org/browse/MXS-2242) MaxScale does not recognize builtin read-only functions
* [MXS-2241](https://jira.mariadb.org/browse/MXS-2241) Conflicting parameters are not detected
* [MXS-2239](https://jira.mariadb.org/browse/MXS-2239) Crash in galeramon
* [MXS-2224](https://jira.mariadb.org/browse/MXS-2224) MaxScale 2.3.2 Memory leaks causes OOM
* [MXS-2217](https://jira.mariadb.org/browse/MXS-2217) maxscale crash with signal 11
* [MXS-2214](https://jira.mariadb.org/browse/MXS-2214) Documentation examples use whitespace in object names, which is invalid
* [MXS-2207](https://jira.mariadb.org/browse/MXS-2207) qc_mysqlembedded does not classify SET STATEMENT ... FOR UPDATE correctly.
* [MXS-2200](https://jira.mariadb.org/browse/MXS-2200) Setting a static variable via maxctrl gives a non accurate error message "Unknown global parameter"
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

50
Documentation/Release-Notes/MaxScale-2.3.4-Release-Notes.md
View File

@ -1,50 +0,0 @@
# MariaDB MaxScale 2.3.4 Release Notes -- 2019-02-13
Release 2.3.4 is a GA release.
This document describes the changes in release 2.3.4, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## New Features
* [MXS-2112](https://jira.mariadb.org/browse/MXS-2112) Create tool to gather a total system report
## Bug fixes
* [MXS-2322](https://jira.mariadb.org/browse/MXS-2322) Null characters in passwords break maxctrl
* [MXS-2315](https://jira.mariadb.org/browse/MXS-2315) std::regex_error exception on csmon startup
* [MXS-2311](https://jira.mariadb.org/browse/MXS-2311) connection_keepalive and error : (4852) Unexpected internal state: received response 0x00 from server
* [MXS-2310](https://jira.mariadb.org/browse/MXS-2310) Cannot create .avsc files if no database connection
* [MXS-2305](https://jira.mariadb.org/browse/MXS-2305) UNIX users are not shown in `maxctrl list users`
* [MXS-2303](https://jira.mariadb.org/browse/MXS-2303) Missing server parameters log wrong error
* [MXS-2300](https://jira.mariadb.org/browse/MXS-2300) Reconnection requirements are too strict
* [MXS-2299](https://jira.mariadb.org/browse/MXS-2299) Routing hints are ignored for multi-statement and SP calls
* [MXS-2295](https://jira.mariadb.org/browse/MXS-2295) COM_CHANGE_USER does not clear out session command history
* [MXS-2268](https://jira.mariadb.org/browse/MXS-2268) readwritesplitter is not routing queries properly in Maxscale 2.3.2
* [MXS-2265](https://jira.mariadb.org/browse/MXS-2265) Timestamp value '0000-00-00 00:00:00' conversion issue
* [MXS-2237](https://jira.mariadb.org/browse/MXS-2237) server status labels are not documented
* [MXS-2038](https://jira.mariadb.org/browse/MXS-2038) debug assert at rwsplit_route_stmt.cc:469 failed: btype != BE_MASTER
* [MXS-1757](https://jira.mariadb.org/browse/MXS-1757) Problem while linking libavrorouter.so
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

60
Documentation/Release-Notes/MaxScale-2.3.5-Release-Notes.md
View File

@ -1,60 +0,0 @@
# MariaDB MaxScale 2.3.5 Release Notes -- 2019-04-02
Release 2.3.5 is a GA release.
This document describes the changes in release 2.3.5, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2412](https://jira.mariadb.org/browse/MXS-2412) Service serialization is broken
* [MXS-2410](https://jira.mariadb.org/browse/MXS-2410) Hangup delivered to wrong DCB
* [MXS-2409](https://jira.mariadb.org/browse/MXS-2409) Schemarouter crashes if PREPARE or EXECUTE is malformed
* [MXS-2403](https://jira.mariadb.org/browse/MXS-2403) Masking filter should check subqueries
* [MXS-2402](https://jira.mariadb.org/browse/MXS-2402) Masking filter should check unions
* [MXS-2398](https://jira.mariadb.org/browse/MXS-2398) Recognize MariaDB specific executable comments
* [MXS-2396](https://jira.mariadb.org/browse/MXS-2396) Masking filter should examine user variables
* [MXS-2394](https://jira.mariadb.org/browse/MXS-2394) global setting "substitute_variables" is rejected as unknown global parameter
* [MXS-2393](https://jira.mariadb.org/browse/MXS-2393) Masking filter should check parse result of query classification.
* [MXS-2392](https://jira.mariadb.org/browse/MXS-2392) Masking filter should examine statement being prepared
* [MXS-2390](https://jira.mariadb.org/browse/MXS-2390) Masking and DBFW filters should reject statement prepared from variable
* [MXS-2389](https://jira.mariadb.org/browse/MXS-2389) Fix executable comment handling
* [MXS-2379](https://jira.mariadb.org/browse/MXS-2379) JSON Interface not work with Maxscale 2.3
* [MXS-2374](https://jira.mariadb.org/browse/MXS-2374) Binlogfilter can break replication if last event is ignored
* [MXS-2373](https://jira.mariadb.org/browse/MXS-2373) Generated configs for filters does not include module
* [MXS-2370](https://jira.mariadb.org/browse/MXS-2370) Query timeout warning message does not print reason of timeout
* [MXS-2368](https://jira.mariadb.org/browse/MXS-2368) maxctrl requires password on command line and cannot change user password
* [MXS-2365](https://jira.mariadb.org/browse/MXS-2365) Wrong classification of queued queries in readwritesplit
* [MXS-2359](https://jira.mariadb.org/browse/MXS-2359) LIKE clause in SHOW TABLES is ignored by schemarouter
* [MXS-2357](https://jira.mariadb.org/browse/MXS-2357) maxctrl documentation for alter service, include use_sql_variables_in
* [MXS-2355](https://jira.mariadb.org/browse/MXS-2355) MaxScale does not let mysql client 8.0.15 to connect with password
* [MXS-2342](https://jira.mariadb.org/browse/MXS-2342) maxadmin commands hang when master pod deleted after failover occurs
* [MXS-2337](https://jira.mariadb.org/browse/MXS-2337) schemarouter in 2.3.4 doesn't show all tables from all backends
* [MXS-2326](https://jira.mariadb.org/browse/MXS-2326) Routing hints are ignored when reconnection is required
* [MXS-2325](https://jira.mariadb.org/browse/MXS-2325) Disabled events are enabled on promoted slave upon failover
* [MXS-2323](https://jira.mariadb.org/browse/MXS-2323) Connections to servers in maintenance aren't closed
* [MXS-2292](https://jira.mariadb.org/browse/MXS-2292) Allow PAM user and group mapping to work with more specific host than '%'
* [MXS-1991](https://jira.mariadb.org/browse/MXS-1991) Why MariaDBMon complain about replication_user and replication_password?
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

53
Documentation/Release-Notes/MaxScale-2.3.6-Release-Notes.md
View File

@ -1,53 +0,0 @@
# MariaDB MaxScale 2.3.6 Release Notes -- 2019-04-23
Release 2.3.6 is a GA release.
This document describes the changes in release 2.3.6, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## New Features
* [MXS-2417](https://jira.mariadb.org/browse/MXS-2417) MaxScale main config should take precedence over runtime config on restart
* [MXS-2344](https://jira.mariadb.org/browse/MXS-2344) Support MASTER_SSL in mariadbmon for encrypting replication traffic
### REST API & MaxCtrl: Hard maintenance mode
The new `--force` option for the `set server` command in MaxCtrl allows all
connections to the server in question to be closed when it is set into
maintenance mode. This causes idle connections to be closed immediately.
For more information, read the
[REST-API](../REST-API/Resources-Server.md#set-server-state) documentation for
the `set` endpoint.
## Bug fixes
* [MXS-2423](https://jira.mariadb.org/browse/MXS-2423) retain_last_statements not in maxctrl show maxscale
* [MXS-2419](https://jira.mariadb.org/browse/MXS-2419) Hangs on query during multiple transaction replays
* [MXS-2418](https://jira.mariadb.org/browse/MXS-2418) Crash on transaction replay if log_info is on and session starts with no master
* [MXS-2416](https://jira.mariadb.org/browse/MXS-2416) Possible memory leak
* [MXS-2324](https://jira.mariadb.org/browse/MXS-2324) Maxscale disconnect after commit without begin from Icinga2
* [MXS-2259](https://jira.mariadb.org/browse/MXS-2259) Maxscale consumes large amounts of memory even with buffer limits set.
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

47
Documentation/Release-Notes/MaxScale-2.3.7-Release-Notes.md
View File

@ -1,47 +0,0 @@
# MariaDB MaxScale 2.3.7 Release Notes -- 2019-05-16
Release 2.3.7 is a GA release.
This document describes the changes in release 2.3.7, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## New Features
* [MXS-1469](https://jira.mariadb.org/browse/MXS-1469) Galeramon: Server-side initiated maintenance mode
## Bug fixes
* [MXS-2474](https://jira.mariadb.org/browse/MXS-2474) Housekeeper allows the registration of the same task multiple times
* [MXS-2472](https://jira.mariadb.org/browse/MXS-2472) BinlogRouter's "Using secondary masters" documentation is incomplete
* [MXS-2457](https://jira.mariadb.org/browse/MXS-2457) MaxScale Mask Filter incorrectly handles ANSI_QUOTES
* [MXS-2450](https://jira.mariadb.org/browse/MXS-2450) Crash on COM_CHANGE_USER with disable_sescmd_history=true
* [MXS-2433](https://jira.mariadb.org/browse/MXS-2433) infinite memory usage, possible leak
* [MXS-2427](https://jira.mariadb.org/browse/MXS-2427) namedserverfilter fails to direct query if first server listed in targetXY is in maintenance mode
* [MXS-2415](https://jira.mariadb.org/browse/MXS-2415) data for new AVRO versions is not send via cdc
* [MXS-2381](https://jira.mariadb.org/browse/MXS-2381) Admin user passwords cannot be changed
* [MXS-2366](https://jira.mariadb.org/browse/MXS-2366) Wrong tarball RPATH
* [MXS-2315](https://jira.mariadb.org/browse/MXS-2315) std::regex_error exception on csmon startup
* [MXS-2046](https://jira.mariadb.org/browse/MXS-2046) Memory leak in binlog router
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

49
Documentation/Release-Notes/MaxScale-2.3.8-Release-Notes.md
View File

@ -1,49 +0,0 @@
# MariaDB MaxScale 2.3.8 Release Notes -- 2019-06-12
Release 2.3.8 is a GA release.
This document describes the changes in release 2.3.8, when compared to the
previous release in the same series.
For any problems you encounter, please consider submitting a bug
report on [our Jira](https://jira.mariadb.org/projects/MXS).
## Bug fixes
* [MXS-2541](https://jira.mariadb.org/browse/MXS-2541) Crash with transaction_replay=true
* [MXS-2538](https://jira.mariadb.org/browse/MXS-2538) MaxScale sends wrong charset in some cases
* [MXS-2536](https://jira.mariadb.org/browse/MXS-2536) Hang on KILL /*QUERY*/ 1
* [MXS-2525](https://jira.mariadb.org/browse/MXS-2525) before upgrade to 2.3, all works well ,after upgrade maxscale to 2.3.7，some programing drivers can not work well
* [MXS-2520](https://jira.mariadb.org/browse/MXS-2520) Readwritesplit won't connect to master for reads
* [MXS-2511](https://jira.mariadb.org/browse/MXS-2511) Maxscale c-connector version
* [MXS-2507](https://jira.mariadb.org/browse/MXS-2507) Hang on CREATE TABLE tab
* [MXS-2496](https://jira.mariadb.org/browse/MXS-2496) Service user with roles causes false warnings
* [MXS-2494](https://jira.mariadb.org/browse/MXS-2494) MySQLAuth load users query doesn't check mysql.user's plugin column for MariaDB 10.1+
* [MXS-2491](https://jira.mariadb.org/browse/MXS-2491) Destructor dependency between different components of the log
* [MXS-2479](https://jira.mariadb.org/browse/MXS-2479) Don't throw error for PAM_TEXT_INFO in PAM conversation function
* [MXS-2473](https://jira.mariadb.org/browse/MXS-2473) Clarify documentation on regex-related options
* [MXS-2464](https://jira.mariadb.org/browse/MXS-2464) Crash in route_stored_query with ReadWriteSplit
* [MXS-2250](https://jira.mariadb.org/browse/MXS-2250) DESCRIBE on temporary table is routed to slave
* [MXS-2083](https://jira.mariadb.org/browse/MXS-2083) Maxadmin list servers gives a negative for the number of connections
* [MXS-1851](https://jira.mariadb.org/browse/MXS-1851) Using backend protocol as client protocol causes a crash
* [MXS-1700](https://jira.mariadb.org/browse/MXS-1700) Using MariaDBClient for backend protocol module causes a crash
## Known Issues and Limitations
There are some limitations and known issues within this version of MaxScale.
For more information, please refer to the [Limitations](../About/Limitations.md) document.
## Packaging
RPM and Debian packages are provided for supported the Linux distributions.
Packages can be downloaded [here](https://mariadb.com/downloads/mariadb-tx/maxscale).
## Source Code
The source code of MaxScale is tagged at GitHub with a tag, which is identical
with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale
is `maxscale-X.Y.Z`. Further, the default branch is always the latest GA version
of MaxScale.
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).

1
server/modules/protocol/MySQL/rwbackend.cc
View File

@ -303,6 +303,7 @@ void RWBackend::process_packets(GWBUF* result)
len |= (*it++) << 16;
++it; // Skip the sequence
mxb_assert(it != buffer.end());
mxb_assert(std::distance(it, buffer.end()) >= len);
auto end = it;
end.advance(len);
uint8_t cmd = *it;