Merge branch '2.3.0' into 2.3
This commit is contained in:
Johan Wikman
commit
7ff69df388
@ -1,292 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.0 Release Notes -- 2017-10-12
|
||||
|
||||
Release 2.2.0 is a Beta release.
|
||||
|
||||
This document describes the changes in release 2.2.0, when compared to
|
||||
release 2.1.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### Whitespace in Object Names
|
||||
|
||||
Significant whitespace in object names is now deprecated. All object names
|
||||
(services, servers, etc.) will be converted to a compatible format by
|
||||
squeezing repeating whitespace and replacing it with hyphens. If any
|
||||
object name conversions take place, a warning will be logged.
|
||||
|
||||
### Monitor Scripts
|
||||
|
||||
The execution of monitor scripts has been made synchronous. This means
|
||||
that a monitor will wait until the executed script is done or until a
|
||||
timeout is exceeded. The timeout is configurable with the `script_timeout`
|
||||
parameter.
|
||||
|
||||
In addition to this, the output of the script is logged into the MaxScale log
|
||||
file. The message is logged on the matching log level if it is prefixed with one
|
||||
of `alert:`, `error:`, `warning:`, `notice:`, `info:` or `debug:`. If no prefix
|
||||
is provided, the message is logged on the notice level.
|
||||
|
||||
For more information, refer to the [monitor documentation](../Monitors/Monitor-Common.md).
|
||||
|
||||
### Read-only Administrative Users
|
||||
|
||||
Users that can only perform read-only operations can be created with `add
|
||||
readonly-user` and `enable readonly-account` commands. To convert
|
||||
administrative users to read-only users, delete the old administrative user and
|
||||
create it as a read-only user.
|
||||
|
||||
For more information about administrative interface users, refer to the
|
||||
[MaxAdmin](../Reference/MaxAdmin.md) documentation.
|
||||
|
||||
**Note:** Old users from pre-2.2 MaxScale versions will be converted to
|
||||
administrative users that have full access to all commands.
|
||||
|
||||
### MaxAdmin
|
||||
|
||||
The `remove user` command now only expects one parameter, the username.
|
||||
|
||||
### Regular Expression Parameters
|
||||
|
||||
Modules may now use a built-in regular expression (regex) string parameter type
|
||||
instead of a normal string when accepting patterns. The regex parameters are
|
||||
checked by the config file loader to compile using the PCRE2 library embedded
|
||||
within MaxScale. The only module using the new regex parameter type is currently
|
||||
*QLAFilter*.
|
||||
|
||||
The only action users should take is enclose their regular expressions in
|
||||
slashes, e.g. `match=/^select/` defines the pattern `^select`. The slashes allow
|
||||
whitespace to be read from the ends of the regex string contrary to a normal
|
||||
string parameter and are removed before compiling the pattern. For backwards
|
||||
compatibility, the slashes are not yet mandatory. Omitting them is, however,
|
||||
deprecated and will be rejected in the next release of MaxScale.
|
||||
|
||||
### `monitor_interval`
|
||||
|
||||
The default value of `monitor_interval` was changed from 10000 milliseconds to
|
||||
2000 milliseconds.
|
||||
|
||||
### NamedServerFilter
|
||||
|
||||
The filter now accepts multiple match-server pairs. Please see the
|
||||
[NamedServerFilter](../Filters/Named-Server-Filter.md) documentation for
|
||||
details.
|
||||
|
||||
### Tee Filter
|
||||
|
||||
The `tee` filter has been rewritten to better suit the way MaxScale now
|
||||
functions. The filter requires that the service where the branched session is
|
||||
created has at least one network listener. The users must also be able to
|
||||
connect from the local MaxScale host. Usually this means that an extra grant for
|
||||
the loopback address is required (e.g. `myuser@127.0.0.1`).
|
||||
|
||||
In addition to the aforementioned requirements, a failure to create a branched
|
||||
session no longer causes the actual client session to be closed. In most cases,
|
||||
this is desired behavior.
|
||||
|
||||
The `match` and `exclude` parameters were changed to use PCRE2 syntax for the
|
||||
regular expressions. The regular expression should be enclosed by slashes
|
||||
e.g. `match=/select.*from.*test/`.
|
||||
|
||||
A tee filter instance can be disabled with the new `tee disable [FILTER]` and
|
||||
`tee enable [FILTER]` module commands. Refer to the
|
||||
[module command documentation](../Reference/Module-Commands.md) for more
|
||||
details on module commands and the
|
||||
[Tee Filter documentation](../Filters/Tee-Filter.md) for details on the tee
|
||||
filter specific commands.
|
||||
|
||||
### Dbfwfilter
|
||||
|
||||
The `function` type rule will now match a query that does not use a function
|
||||
when the filter is in whitelist mode (`action=allow`). This means that queries
|
||||
that don't use functions are allowed though in whitelist mode.
|
||||
|
||||
#### Rule Names
|
||||
|
||||
Rule names can no longer use punctuation in them and can consist only of
|
||||
alphanumeric characters, underscores and hyphens.
|
||||
|
||||
#### Keywords `deny` and `allow`
|
||||
|
||||
The `deny` and `allow` keywords are deprecated in favor of the more descriptive
|
||||
`match` keyword. All instances of `deny` and `allow` can be replaced with
|
||||
`match` with no functional changes.
|
||||
|
||||
### Logging
|
||||
|
||||
When known, the session id will be included in all logged messages. This allows
|
||||
a range of logged messages related to a particular session (that is, client) to
|
||||
be bound together, and makes it easier to investigate problems. In practice this
|
||||
is visible so that if a logged message earlier looked like
|
||||
```
|
||||
2017-08-30 12:20:49 warning: [masking] The rule ...
|
||||
```
|
||||
it will now look like
|
||||
```
|
||||
2017-08-30 12:20:49 warning: (4711) [masking] The rule ...
|
||||
```
|
||||
where `4711` is the session id.
|
||||
|
||||
### Binlogrouter Default Values
|
||||
|
||||
The _binlogdir_ now has a default value of `/var/lib/maxscale/`. Previously the
|
||||
parameter was mandatory even though it was documented to have a default value.
|
||||
|
||||
The _mariadb10-compatibility_ is enabled by default since MaxScale 2.2.0. This
|
||||
allows easier use of the MariaDB 10 series server.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
### MaxAdmin
|
||||
|
||||
The following deprecated commands have been removed:
|
||||
|
||||
* `enable log [debug|trace|message]`
|
||||
* `disable log [debug|trace|message]`
|
||||
* `enable sessionlog [debug|trace|message]`
|
||||
* `disable sessionlog [debug|trace|message]`
|
||||
|
||||
The following commands have been deprecated:
|
||||
|
||||
* `enable sessionlog-priority <session-id> [debug|info|notice|warning]`
|
||||
* `disable sessionlog-priority <session-id> [debug|info|notice|warning]`
|
||||
* `reload config`
|
||||
|
||||
The `{ enable | disable } sessionlog-priority` commands can be issued, but they
|
||||
have no effect.
|
||||
|
||||
#### Filenames as MaxAdmin Arguments
|
||||
|
||||
MaxAdmin no longer attempts to interpret additional command line parameters as a
|
||||
file name to load commands from (e.g. `maxadmin mycommands.txt`). The shell
|
||||
indirection operator `<` should be used to achieve the same effect (`maxadmin <
|
||||
mycommands.txt`).
|
||||
|
||||
## New Features
|
||||
|
||||
### REST API
|
||||
|
||||
MariaDB MaxScale now exposes a REST-API for obtaining information about
|
||||
and for manipulating the resources of MaxScale. For more information please
|
||||
refer to the [REST API](../REST-API/API.md) documentation.
|
||||
|
||||
### MaxCtrl Command Line Client
|
||||
|
||||
The MaxCtrl is a new command line intended to replace MaxAdmin. This
|
||||
client uses the REST API to communicate with MaxScale in a secure way. The
|
||||
client is distributed separately in the `maxscale-client` package.
|
||||
|
||||
For more information, refer to the [MaxCtrl](../Reference/MaxCtrl.md)
|
||||
documentation.
|
||||
|
||||
### Limited support from Pluggable Authentication Modules (PAM).
|
||||
|
||||
Pluggable authentication module (PAM) is a general purpose authentication API.
|
||||
An application using PAM can authenticate a user without knowledge about the
|
||||
underlying authentication implementation. For more information please refer to
|
||||
the [PAM Authenticator](../Authenticators/PAM-Authenticator.md) documentation.
|
||||
|
||||
### MySQL Monitor Crash Safety
|
||||
|
||||
The MySQL monitor keeps a journal of the state of the servers and the currently
|
||||
elected master. This information will be read if MaxScale suffers an
|
||||
uncontrolled shutdown. By doing the journaling of server states, the mysqlmon
|
||||
monitor is able to keep track of stale master and stale slave states across
|
||||
restarts and crashes.
|
||||
|
||||
### New Variables for Monitor Scripts
|
||||
|
||||
The PARENT and CHILDREN variables were added to the monitor scripts. The former
|
||||
expands to the direct parent node of the server that triggers the event and the
|
||||
latter expands to a list of servers that are direct descendants of the server
|
||||
that triggered the event.
|
||||
|
||||
For more information, refer to the [monitor documentation](../Monitors/Monitor-Common.md).
|
||||
|
||||
### Avrorouter `deflate` compression
|
||||
|
||||
The Avrorouter now supports the `deflate` compression method. This allows the
|
||||
stored Avro format files to be compressed on disk. For more information, refer
|
||||
to the [Avrorouter](../Routers/Avrorouter.md) documentation.
|
||||
|
||||
### Preliminary proxy protocol support
|
||||
|
||||
The MySQL backend protocol module now supports sending a proxy protocol header
|
||||
to the server. For more information, see the server section in the
|
||||
[Configuration guide](../Getting-Started/Configuration-Guide.md).
|
||||
|
||||
### KILL command support
|
||||
|
||||
The MySQL client protocol now supports execution of `KILL` statements through
|
||||
MaxScale. The connection IDs in these queries will be transformed into the
|
||||
correct ones by MaxScale.
|
||||
|
||||
`KILL QUERY ID <query_id>` is not supported by MaxScale and it needs to be
|
||||
executed directly on the relevant backend server. In addition to this, there are
|
||||
minor limitations to the `KILL` command handling. See
|
||||
[Limitations](../About/Limitations.md) for more information.
|
||||
|
||||
### Obfuscation and partial masking added to the masking filter.
|
||||
|
||||
A value can now be obfuscated instead of just masked. Further, it is
|
||||
possible to specify with a regular expression that only a specific part
|
||||
of a value should be masked. For more information, please read the
|
||||
[masking filter](../Filters/Masking.md) documentation.
|
||||
|
||||
### New rules for dbfwfilter
|
||||
|
||||
The `uses_function` type rule prevents certain columns from being used
|
||||
with functions. It is now also possible to match a function if it is
|
||||
used in conjunction with specific columns. For more information about
|
||||
the new rules, read the
|
||||
[dbfwfilter](../Filters/Database-Firewall-Filter.md) documentation.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.2.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.2.0)
|
||||
|
||||
* [MXS-1450](https://jira.mariadb.org/browse/MXS-1450) Maxadmin commands with a leading space are silently ignored
|
||||
* [MXS-1449](https://jira.mariadb.org/browse/MXS-1449) Database change not allowed
|
||||
* [MXS-1405](https://jira.mariadb.org/browse/MXS-1405) Script launched by monitors should run synchronously
|
||||
* [MXS-1397](https://jira.mariadb.org/browse/MXS-1397) ReadWriteSplit's master connection can time out if session only issues read-only queries
|
||||
* [MXS-1359](https://jira.mariadb.org/browse/MXS-1359) qc_sqlite crashes with a very large compound select
|
||||
* [MXS-1351](https://jira.mariadb.org/browse/MXS-1351) Partially authenticated connections are put into the connection pool
|
||||
* [MXS-1349](https://jira.mariadb.org/browse/MXS-1349) qc_mysqlembedded accesses wrong preparable statement field
|
||||
* [MXS-1346](https://jira.mariadb.org/browse/MXS-1346) Function blocking per column
|
||||
* [MXS-1345](https://jira.mariadb.org/browse/MXS-1345) Empty function list is not allowed
|
||||
* [MXS-1340](https://jira.mariadb.org/browse/MXS-1340) Report true table and not alias name
|
||||
* [MXS-1339](https://jira.mariadb.org/browse/MXS-1339) QC should return a particular table/database just once
|
||||
* [MXS-1334](https://jira.mariadb.org/browse/MXS-1334) Build on FreeBSD 11 looks for libdl - how can it be told not to?
|
||||
* [MXS-1322](https://jira.mariadb.org/browse/MXS-1322) Flushing log should reopen not reopen and truncate.
|
||||
* [MXS-1307](https://jira.mariadb.org/browse/MXS-1307) Add CTE tests
|
||||
* [MXS-1265](https://jira.mariadb.org/browse/MXS-1265) strerror_r calls result in compiler warnings
|
||||
* [MXS-1262](https://jira.mariadb.org/browse/MXS-1262) Mantenance bit(s) should persist after maxscale restart
|
||||
* [MXS-1221](https://jira.mariadb.org/browse/MXS-1221) Nagios plugin scripts does not process -S option properly
|
||||
* [MXS-1214](https://jira.mariadb.org/browse/MXS-1214) Streaming Insert Filter gives errors
|
||||
* [MXS-1203](https://jira.mariadb.org/browse/MXS-1203) Batch inserts through Maxscale with C/J stall
|
||||
* [MXS-1198](https://jira.mariadb.org/browse/MXS-1198) Interface retry bind interval (of a listener) increases by ten seconds every time it fails (10,20,30,....) it should be a fixed interval (and maybe configurable)
|
||||
* [MXS-1160](https://jira.mariadb.org/browse/MXS-1160) Load infile not working on Schemarouter
|
||||
* [MXS-1146](https://jira.mariadb.org/browse/MXS-1146) JDBC connection dropping transaction when connecting to MaxScale directly
|
||||
* [MXS-959](https://jira.mariadb.org/browse/MXS-959) KILL command on wrong connection ID
|
||||
|
||||
## 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).
|
||||
@ -1,246 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.1 Release Notes -- 2018-01-11
|
||||
|
||||
Release 2.2.1 is a Beta release.
|
||||
|
||||
This document describes the changes in release 2.2.1, when compared to
|
||||
release 2.2.0.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### Process identity
|
||||
|
||||
By default, MaxScale can no longer be run as `root`, but must be run as some
|
||||
other user. However, it is possible to start MaxScale as `root`, as long as
|
||||
the user to run MaxScale as is provided as a command line argument:
|
||||
```
|
||||
root@host:~# maxscale --user=maxuser ...
|
||||
```
|
||||
If it is imperative to run MaxScale as root, e.g. in a Docker container, it
|
||||
can be achieved by invoking MaxScale as root and by explicitly specifying
|
||||
the user to also be root:
|
||||
```
|
||||
root@host:~# maxscale --user=root ...
|
||||
```
|
||||
|
||||
### Binlog server
|
||||
|
||||
* The `mariadb10_slave_gtid` parameter was removed and slave connections can now
|
||||
always register with MariaDB 10 GTID.
|
||||
This means the gtid_maps SQLite database is always updated.
|
||||
|
||||
* The `binlog_structure` parameter was removed and the binlogs are stored
|
||||
automatically in 'tree' mode when `mariadb10_master_gtid` is enabled
|
||||
(GTID registration to master).
|
||||
|
||||
* If `mariadb10_master_gtid` is enabled, the `transaction_safety` is
|
||||
automatically enabled. In MaxScale 2.2.0, if `transaction_safety` was disabled
|
||||
when `mariadb10_master_gtid` was enabled MaxScale would refuse to start.
|
||||
|
||||
* The binlogrouter can accept GTID slave registration from MariaDB 10.X slaves
|
||||
and can also register to Master server MariaDB 10.x using GTID.
|
||||
|
||||
### Module names and case sensitivity
|
||||
|
||||
* The filenames of all modules have been made lowercase.
|
||||
* When specifying a module, the name matching is case insensitive.
|
||||
|
||||
In practice this means that in the configuration file, the following
|
||||
are all equivalent:
|
||||
```
|
||||
router=readwritesplit
|
||||
|
||||
router=READWRITESPLIT
|
||||
|
||||
router=ReadWriteSplit
|
||||
```
|
||||
|
||||
### MySQL/MariaDB Client Protocol
|
||||
|
||||
The shared object implementing the client protocol has been renamed
|
||||
from `libMySQLClient.so` to `libmaridbclient.so`. In practice this means
|
||||
that, in the MaxScale configuration file, `MySQLClient` should be replaced
|
||||
with `mariadbclient` or, e.g., `MariaDBClient`, as module names are matched
|
||||
in a case insensitive manner.
|
||||
|
||||
As an example, a listener section like
|
||||
```
|
||||
[TheListener]
|
||||
type=listener
|
||||
...
|
||||
protocol=MySQLClient
|
||||
```
|
||||
should be changed into
|
||||
```
|
||||
[TheListener]
|
||||
type=listener
|
||||
...
|
||||
protocol=MariaDBClient
|
||||
```
|
||||
*NOTE* Using `MySQLClient` is still supported, but has been deprecated.
|
||||
|
||||
### MySQL Backend Protocol
|
||||
|
||||
The shared object implementing the backend protocol has been renamed
|
||||
from `libMySQLBackend.so` to `libmaridbbackend.so`. In practice this means
|
||||
that, in the MaxScale configuration file, `MySQLBackend` should be replaced
|
||||
with `mariadbbackend` or, e.g., `MariaDBBackend`, as module names are matched
|
||||
in a case insensitive manner.
|
||||
|
||||
As an example, a server section like
|
||||
```
|
||||
[TheServer]
|
||||
type=server
|
||||
...
|
||||
protocol=MySQLBackend
|
||||
```
|
||||
should be changed into
|
||||
```
|
||||
[TheServer]
|
||||
type=server
|
||||
...
|
||||
protocol=MariaDBBackend
|
||||
```
|
||||
*NOTE* Using `MySQLBackend` is still supported, but has been deprecated.
|
||||
|
||||
### MySQL Monitor
|
||||
|
||||
Renamed to [MariaDB Monitor](../Monitors/MariaDB-Monitor.md).
|
||||
|
||||
Note that this affects the module name as well. Up until MaxScale 2.2.0
|
||||
a configuration section referring to this monitor would look like
|
||||
```
|
||||
[MyMonitor]
|
||||
type=monitor
|
||||
module=mysqlmon
|
||||
...
|
||||
```
|
||||
but from MaxScale 2.2.1 onwards it should look like
|
||||
```
|
||||
[MyMonitor]
|
||||
type=monitor
|
||||
module=mariadbmon
|
||||
...
|
||||
```
|
||||
The name `mysqlmon` has been deprecated but can still be used, although it will
|
||||
cause a warning to be logged.
|
||||
|
||||
### MariaDB Monitor
|
||||
|
||||
The default value of the configuration parameter `detect_standalone_master` has
|
||||
been changed from `false` to `true`.
|
||||
|
||||
### ReadWritesplit
|
||||
|
||||
The default value of `strict_multi_stmt` was changed to `false` to make
|
||||
usage of atomic compound statements and multi-statement queries less
|
||||
restrictive and to align it with the default value of `strict_sp_calls`.
|
||||
|
||||
Most cases where the functionality of `strict_multi_stmt` was triggered
|
||||
were cases where the added safety of locking a session to the master did
|
||||
more harm than it did good.
|
||||
|
||||
The only case where `strict_multi_stmt` should be enabled is when a
|
||||
multi-statement or a compound statement modifies the state of the
|
||||
session. This is not a good practice and a change in the client side
|
||||
behavior is advised.
|
||||
|
||||
### Top Filter
|
||||
|
||||
The top filter now uses the session ID instead of an internal counter for the
|
||||
names of the log file names.
|
||||
|
||||
### MaxCtrl
|
||||
|
||||
The `-h, --hosts` argument was changed to accept a list of hostnames separated
|
||||
by commas instead of spaces. This prevents commands from accidentally being
|
||||
interpreted as hostnames.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
## New Features
|
||||
|
||||
### MariaDB Monitor
|
||||
|
||||
MariaDB Monitor can now perform *failover* (replace a dead master), *switchover*
|
||||
(replace a running master) and *rejoin* (join a standalone node to the
|
||||
master-slave cluster). All of these features only work with a simple 1-master
|
||||
N-slaves cluster using Gtid replication. Failover and switchover can be
|
||||
activated through maxadmin or the REST-API. Failover and rejoin can be set to
|
||||
activate automatically. For more information, see the
|
||||
[MariaDB Monitor documentation](../Monitors/MariaDB-Monitor.md).
|
||||
|
||||
### REST API Relationship Endpoints
|
||||
|
||||
The _servers_, _monitors_ and _services_ types now support direct updating of
|
||||
relationships via the `relationships` endpoints. This conforms to the JSON API
|
||||
specification on updating resource relationships.
|
||||
|
||||
For more information, refer to the REST API documentation. An example of this
|
||||
can be found in the
|
||||
[Server Resource documentation](../REST-API/Resources-Server.md#update-server-relationships).
|
||||
|
||||
### PL/SQL Comaptibility
|
||||
|
||||
The parser of MaxScale has been extended to support the PL/SQL compatibility
|
||||
features of the upcoming 10.3 release. For more information on how to enable
|
||||
this mode, please refer to the
|
||||
[configuration guide](../Getting-Started/Configuration-Guide.md#sql_mode).
|
||||
|
||||
This functionality was available already in MaxScale 2.2.0.
|
||||
|
||||
### Environment Variables in the configuration file
|
||||
|
||||
If the global configuration entry `substitute_variables` is set to true,
|
||||
then if the first character of a value in the configuration file is a `$`
|
||||
then everything following that is interpreted as an environment variable
|
||||
and the configuration value is replaced with the value of the environment
|
||||
variable. For more information please consult the
|
||||
[Configuration Guide](../Getting-Started/Configuration-Guide.md).
|
||||
|
||||
### Cache behaviour in transactions
|
||||
|
||||
It can now be specified how the cache should be behave when a transaction
|
||||
is active. Please refer to the [documentation](../Filters/Cache.md)
|
||||
for details.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.2.1.](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.2.1)
|
||||
|
||||
* [MXS-1593](https://jira.mariadb.org/browse/MXS-1593) Servers appearing as Stale out of list servers for a fresh setup
|
||||
* [MXS-1588](https://jira.mariadb.org/browse/MXS-1588) Switchover fails randomly
|
||||
* [MXS-1582](https://jira.mariadb.org/browse/MXS-1582) Maxscale leaving socket behind after shutdown
|
||||
* [MXS-1545](https://jira.mariadb.org/browse/MXS-1545) Fix GTID connecting slave error detections
|
||||
* [MXS-1541](https://jira.mariadb.org/browse/MXS-1541) Top filter uses internal ID instead of session ID for file suffix
|
||||
* [MXS-1527](https://jira.mariadb.org/browse/MXS-1527) SELECT with session var is not supported
|
||||
* [MXS-1525](https://jira.mariadb.org/browse/MXS-1525) Firewall filter does not check exact match for host
|
||||
* [MXS-1519](https://jira.mariadb.org/browse/MXS-1519) Firewall instances can interfere with each other
|
||||
* [MXS-1517](https://jira.mariadb.org/browse/MXS-1517) Retain stale master status even if the master goes down
|
||||
* [MXS-1499](https://jira.mariadb.org/browse/MXS-1499) Add missing fields to SHOW ALL SLAVES STATUS
|
||||
* [MXS-1486](https://jira.mariadb.org/browse/MXS-1486) The cache does not always update the cached entry even if it could
|
||||
* [MXS-1461](https://jira.mariadb.org/browse/MXS-1461) NOT operation needed for firewall rule
|
||||
* [MXS-1408](https://jira.mariadb.org/browse/MXS-1408) maxadmin not working in latest version
|
||||
* [MXS-1327](https://jira.mariadb.org/browse/MXS-1327) set log-priority by maxadmin
|
||||
|
||||
## 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).
|
||||
@ -1,47 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.10 Release Notes -- 2018-06-28
|
||||
|
||||
Release 2.2.10 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.10, when compared to
|
||||
release 2.2.9.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1935](https://jira.mariadb.org/browse/MXS-1935) PREPARE ... FROM @var is not parsed
|
||||
* [MXS-1932](https://jira.mariadb.org/browse/MXS-1932) MaxScale reads hidden files from maxscale.cnf.d
|
||||
* [MXS-1931](https://jira.mariadb.org/browse/MXS-1931) Debug assertion in is_large_query fails
|
||||
* [MXS-1930](https://jira.mariadb.org/browse/MXS-1930) New capability flags aren't used with MariaDB 10.3
|
||||
* [MXS-1926](https://jira.mariadb.org/browse/MXS-1926) LOAD DATA LOCAL INFILE interrupted by slave shutdown
|
||||
* [MXS-1920](https://jira.mariadb.org/browse/MXS-1920) # is not recognized as an until-end-of-line comment character
|
||||
* [MXS-1913](https://jira.mariadb.org/browse/MXS-1913) fatal signal 11
|
||||
* [MXS-1911](https://jira.mariadb.org/browse/MXS-1911) Certificate verification cannot be disabled for created listeners
|
||||
* [MXS-1910](https://jira.mariadb.org/browse/MXS-1910) Only ssl_ca_cert should be required for servers
|
||||
* [MXS-1907](https://jira.mariadb.org/browse/MXS-1907) Can't define ssl_verify_peer_certificate at runtime
|
||||
* [MXS-1902](https://jira.mariadb.org/browse/MXS-1902) COM_CHANGE_USER lost connection
|
||||
* [MXS-1891](https://jira.mariadb.org/browse/MXS-1891) DEALLOCATE PREPARE should route to all
|
||||
* [MXS-1887](https://jira.mariadb.org/browse/MXS-1887) Using cache causes slow read from mysql server
|
||||
* [MXS-1749](https://jira.mariadb.org/browse/MXS-1749) Process datadir is not always deleted on exit
|
||||
* [MXS-872](https://jira.mariadb.org/browse/MXS-872) MaxScale doesn't understand roles
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,47 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.11 Release Notes -- 2018-07-05
|
||||
|
||||
Release 2.2.11 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.11, when compared to
|
||||
release 2.2.10.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### Cache
|
||||
|
||||
The cache filter is no longer marked as being experimental. The default
|
||||
value for `cached_data` been changed from `shared` to `thread_specific`,
|
||||
and the default value for `selects` has been changed from `verify_cacheable`
|
||||
to `assume_cacheable`.
|
||||
Please consult the
|
||||
[cache documentation](../Filters/Cache.md)
|
||||
for details.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1953](https://jira.mariadb.org/browse/MXS-1953) MaxScale hangs
|
||||
* [MXS-1950](https://jira.mariadb.org/browse/MXS-1950) No explanation for routing failure when no valid servers are available
|
||||
* [MXS-1948](https://jira.mariadb.org/browse/MXS-1948) Connections not balanced between workers
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,44 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.12 Release Notes -- 2018-7-27
|
||||
|
||||
Release 2.2.12 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.12, when compared to
|
||||
release 2.2.11.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report on [our Jira](https://jira.mariadb.org/projects/MXS).
|
||||
|
||||
## New Features
|
||||
|
||||
### Configuration Exporting
|
||||
|
||||
The runtime configuration can now be dumped into a file with the
|
||||
`--export-config` command line option. This allows changes done at runtime to be
|
||||
collected into a single file for easier exporting.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1985](https://jira.mariadb.org/browse/MXS-1985) Concurrent KILL commands cause deadlock
|
||||
* [MXS-1977](https://jira.mariadb.org/browse/MXS-1977) Maxscale 2.2.6 memory leak
|
||||
* [MXS-1949](https://jira.mariadb.org/browse/MXS-1949) Warning for user load failure logged even when service has no users
|
||||
* [MXS-1942](https://jira.mariadb.org/browse/MXS-1942) maxctrl --version is not helpful
|
||||
|
||||
## 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,35 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.13 Release Notes -- 2018-08-08
|
||||
|
||||
Release 2.2.13 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.13, when compared to
|
||||
release 2.2.12.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report on [our Jira](https://jira.mariadb.org/projects/MXS).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1997](https://jira.mariadb.org/browse/MXS-1997) Object names are limited to 49 characters
|
||||
* [MXS-1983](https://jira.mariadb.org/browse/MXS-1983) Failed to add dcb to epoll set
|
||||
* [MXS-1961](https://jira.mariadb.org/browse/MXS-1961) Standalone master loses master status
|
||||
|
||||
## Known Issues and Limitations
|
||||
|
||||
There are some limitations and known issues within this version of MaxScale.
|
||||
For more information, please refer to the [Limitations](../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,56 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.14 Release Notes -- 2018-09-17
|
||||
|
||||
Release 2.2.14 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.14, 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-2039](https://jira.mariadb.org/browse/MXS-2039) Filter tables in avrorouter
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-2046](https://jira.mariadb.org/browse/MXS-2046) Memory leak in binlog router
|
||||
* [MXS-2042](https://jira.mariadb.org/browse/MXS-2042) Hang with multistatment queries
|
||||
* [MXS-2041](https://jira.mariadb.org/browse/MXS-2041) Crash on failure to create schemarouter session
|
||||
* [MXS-2040](https://jira.mariadb.org/browse/MXS-2040) Default monitor timeouts are too short
|
||||
* [MXS-2037](https://jira.mariadb.org/browse/MXS-2037) % wildcards not working with source in Named Server Filter
|
||||
* [MXS-2036](https://jira.mariadb.org/browse/MXS-2036) A slave with sql thread stopped causes wrong master after failover
|
||||
* [MXS-2035](https://jira.mariadb.org/browse/MXS-2035) available_when_donor don't working with mariabackup sst method
|
||||
* [MXS-2034](https://jira.mariadb.org/browse/MXS-2034) query_retry_timeout was not set
|
||||
* [MXS-2033](https://jira.mariadb.org/browse/MXS-2033) MASTER_SSL_KEY and MASTER_SSL_CERT should not be required
|
||||
* [MXS-2027](https://jira.mariadb.org/browse/MXS-2027) LOAD DATA LOCAL INFILE is not ignored by protocol modules
|
||||
* [MXS-2024](https://jira.mariadb.org/browse/MXS-2024) Crash in reauthenticate_client
|
||||
* [MXS-2019](https://jira.mariadb.org/browse/MXS-2019) All atexit handlers aren't called
|
||||
* [MXS-2015](https://jira.mariadb.org/browse/MXS-2015) CDC Connector ignores errors after registration is successful
|
||||
* [MXS-2007](https://jira.mariadb.org/browse/MXS-2007) Fatal: MaxScale 2.2.13 received fatal signal 11 (Aurora Monitor)
|
||||
* [MXS-1999](https://jira.mariadb.org/browse/MXS-1999) Invalid null relationship handling in REST API
|
||||
* [MXS-1996](https://jira.mariadb.org/browse/MXS-1996) Avrorouter writes misleading error messages to the log
|
||||
* [MXS-1947](https://jira.mariadb.org/browse/MXS-1947) Composite roles are not supported
|
||||
* [MXS-1880](https://jira.mariadb.org/browse/MXS-1880) MaxScale 2.2.5-1 Crashes after a non clean Start
|
||||
* [MXS-1736](https://jira.mariadb.org/browse/MXS-1736) Clarify the usage of maxpasswd in documentation
|
||||
* [MXS-1735](https://jira.mariadb.org/browse/MXS-1735) Clarify SSL 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).
|
||||
@ -1,38 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.15 Release Notes -- 2018-10-01
|
||||
|
||||
Release 2.2.15 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.15, 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-2066](https://jira.mariadb.org/browse/MXS-2066) Result buffering is not always disabled
|
||||
* [MXS-2064](https://jira.mariadb.org/browse/MXS-2064) Loading of users with MariaDB 10.2.10 fails
|
||||
* [MXS-2060](https://jira.mariadb.org/browse/MXS-2060) Users are loaded from servers in maintenance
|
||||
* [MXS-2052](https://jira.mariadb.org/browse/MXS-2052) readwritesplit doesn't explain why session closes
|
||||
* [MXS-2045](https://jira.mariadb.org/browse/MXS-2045) Avrorouter tutorial is not good enough
|
||||
* [MXS-2043](https://jira.mariadb.org/browse/MXS-2043) Error "The MariaDB server is running with the --read-only option" for "select for update"
|
||||
|
||||
## 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,100 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.2 Release Notes -- 2018-02-19
|
||||
|
||||
Release 2.2.2 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.2, when compared to
|
||||
release 2.2.1.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### MaxCtrl Moved to `maxscale` Package
|
||||
|
||||
The MaxCtrl client is now a part of the main MaxScale package, `maxscale`. This
|
||||
means that the `maxctrl` executable is now immediately available upon the
|
||||
installation of MaxScale.
|
||||
|
||||
In the 2.2.1 beta version MaxCtrl was in its own package. If you have a previous
|
||||
installation of MaxCtrl, please remove it before upgrading to MaxScale 2.2.2.
|
||||
|
||||
### MaxScale C++ CDC Connector Integration
|
||||
|
||||
The MaxScale C++ CDC Connector is now distributed as a part of MaxScale. The
|
||||
connector libraries are in a separate package, `maxscale-cdc-connector`. Refer
|
||||
to the [CDC Connector documentation](../Connectors/CDC-Connector.md) for more details.
|
||||
|
||||
### Output of `show threads` has changed.
|
||||
|
||||
For each thread is shown what state it is in, how many descriptors are currently
|
||||
in the thread's epoll instance and how many descriptors in total have been in the
|
||||
thread's epoll instance.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
## New Features
|
||||
|
||||
### Users Refresh Time
|
||||
|
||||
It is now possible to adjust how frequently MaxScale may refresh
|
||||
the users of service. Please refer to the documentation for
|
||||
[details](../Getting-Started/Configuration-Guide.md#users_refresh_time).
|
||||
|
||||
### Local Address
|
||||
|
||||
It is now possible to specify what local address MaxScale should
|
||||
use when connecting to servers. Please refer to the documentation
|
||||
for [details](../Getting-Started/Configuration-Guide.md#local_address).
|
||||
|
||||
### External master support for failover/switchover
|
||||
|
||||
Failover/switchover now tries to preserve replication from an external master
|
||||
server. Check
|
||||
[MariaDB Monitor documentation](../Monitors/MariaDB-Monitor.md#external-master-support)
|
||||
for more information.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.2.2.](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.2.2)
|
||||
|
||||
* [MXS-1661](https://jira.mariadb.org/browse/MXS-1661) Excessive logging by MySQLAuth at authentication error (was: MySQLAuth SQLite database can be permanently locked)
|
||||
* [MXS-1660](https://jira.mariadb.org/browse/MXS-1660) Failure to resolve hostname is considered an error
|
||||
* [MXS-1654](https://jira.mariadb.org/browse/MXS-1654) MaxScale crashes if env-variables are used without substitute_variables=1 having been defined
|
||||
* [MXS-1653](https://jira.mariadb.org/browse/MXS-1653) sysbench failed to initialize w/ MaxScale read/write splitter
|
||||
* [MXS-1647](https://jira.mariadb.org/browse/MXS-1647) Module API version is not checked
|
||||
* [MXS-1643](https://jira.mariadb.org/browse/MXS-1643) Too many monitor events are triggered
|
||||
* [MXS-1641](https://jira.mariadb.org/browse/MXS-1641) Fix overflow in master id
|
||||
* [MXS-1633](https://jira.mariadb.org/browse/MXS-1633) Need remove mutex in sqlite
|
||||
* [MXS-1630](https://jira.mariadb.org/browse/MXS-1630) MaxCtrl binary are not included by default in MaxScale package
|
||||
* [MXS-1628](https://jira.mariadb.org/browse/MXS-1628) Security scanner says MaxScale is vulnerable to ancient MySQL vulnerability
|
||||
* [MXS-1620](https://jira.mariadb.org/browse/MXS-1620) CentOS package symbols are stripped
|
||||
* [MXS-1615](https://jira.mariadb.org/browse/MXS-1615) Masking filter accesses wrong command argument.
|
||||
* [MXS-1614](https://jira.mariadb.org/browse/MXS-1614) MariaDBMon yet adding mysqlbackend as the protocol instead of mariadbbackend
|
||||
* [MXS-1606](https://jira.mariadb.org/browse/MXS-1606) After enabling detect_replication_lag MariaDBMon does not create the maxscale_schema.replication_heartbeat database and table
|
||||
* [MXS-1604](https://jira.mariadb.org/browse/MXS-1604) PamAuth Default Authentication is Different from MariaDB
|
||||
* [MXS-1591](https://jira.mariadb.org/browse/MXS-1591) Adding get_lock and release_lock support
|
||||
* [MXS-1586](https://jira.mariadb.org/browse/MXS-1586) Mysqlmon switchover does not immediately detect bad new master
|
||||
* [MXS-1583](https://jira.mariadb.org/browse/MXS-1583) Database firewall filter failing with multiple users statements in rules file
|
||||
* [MXS-1539](https://jira.mariadb.org/browse/MXS-1539) Authentication data should be thread specific
|
||||
* [MXS-1508](https://jira.mariadb.org/browse/MXS-1508) Failover is sometimes triggered on non-simple topologies
|
||||
|
||||
## 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).
|
||||
@ -1,65 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.3 Release Notes -- 2018-03-09
|
||||
|
||||
Release 2.2.3 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.3, when compared to
|
||||
release 2.2.2.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### GTID output in MaxCtrl `list servers`
|
||||
|
||||
The output of the `list servers` command now has a GTID column. If a server is
|
||||
being monitored by the mariadbmon monitor, the current GTID position will be
|
||||
displayed in the newly added column. If no GTID is available, an empty value is
|
||||
returned.
|
||||
|
||||
### MaxAdmin input from scripts
|
||||
|
||||
The failure to set terminal attributes for MaxScale is no longer considered an
|
||||
error as scripts most often do not have an actual terminal that control the
|
||||
process. This means that passwords and other commands can be passed to MaxAdmin
|
||||
without a controlling terminal.
|
||||
|
||||
### MaxCtrl password input
|
||||
|
||||
MaxCtrl can now query the password from the user. This allows passwords to be
|
||||
given without giving them as process arguments.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
## New Features
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed in MaxScale 2.2.3.](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.2.3)
|
||||
|
||||
* [MXS-1698](https://jira.mariadb.org/browse/MXS-1698) error:140940F5:SSL routines:ssl3_read_bytes:unexpected record
|
||||
* [MXS-1697](https://jira.mariadb.org/browse/MXS-1697) MaxScale 2.2.2 missing avrorouter library
|
||||
* [MXS-1693](https://jira.mariadb.org/browse/MXS-1693) In Maxscale 2.2.2 getting users with native password from mysql backends does not work
|
||||
* [MXS-1688](https://jira.mariadb.org/browse/MXS-1688) Some date functions are not parsed properly with schemarouter
|
||||
* [MXS-1684](https://jira.mariadb.org/browse/MXS-1684) Empty space on a line in rule file confuses dbfwfilter which refuses to start
|
||||
* [MXS-1683](https://jira.mariadb.org/browse/MXS-1683) Commands that take passwords should allow input from stdin and not just from controlling terminals
|
||||
|
||||
## 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).
|
||||
@ -1,66 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.4 Release Notes -- 2018-03-28
|
||||
|
||||
Release 2.2.4 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.4, when compared to
|
||||
release 2.2.3.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
### Masking is stricter
|
||||
|
||||
If a masking rule specifies the table/database in addition to the column
|
||||
name, then if a resultset does not contain table/database information, it
|
||||
is considered a match if the column name matches. Please consult the
|
||||
[documentation](../Filters/Masking.md) for details.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
## New Features
|
||||
|
||||
New configuration parameters `retain_last_statements` and
|
||||
`dump_last_statements` that can be of help when debugging problems. Please
|
||||
see the [configuration guide](../Getting-Started/Configuration-Guide.md)
|
||||
for details.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1738](https://jira.mariadb.org/browse/MXS-1738) MaxScale crashes in debug mode if authentication fails.
|
||||
* [MXS-1733](https://jira.mariadb.org/browse/MXS-1733) Data masking does not work with UNION queries
|
||||
* [MXS-1731](https://jira.mariadb.org/browse/MXS-1731) Empty version_string is not detected
|
||||
* [MXS-1730](https://jira.mariadb.org/browse/MXS-1730) Column alias named engine without backticks returns an error
|
||||
* [MXS-1729](https://jira.mariadb.org/browse/MXS-1729) Luafilter ignores return value of global routeQuery function
|
||||
* [MXS-1722](https://jira.mariadb.org/browse/MXS-1722) Switchover leads to error: Demotion failed due to an error in updating gtid:s.
|
||||
* [MXS-1721](https://jira.mariadb.org/browse/MXS-1721) If two services share one filter there will a crash at exit.
|
||||
* [MXS-1719](https://jira.mariadb.org/browse/MXS-1719) masking filter with readwritesplit router problems
|
||||
* [MXS-1717](https://jira.mariadb.org/browse/MXS-1717) When having two listeners use the same service show dbusers serviceName shows the user list twice
|
||||
* [MXS-1716](https://jira.mariadb.org/browse/MXS-1716) show dbusers ...service... returns empty list when using PAMAuth
|
||||
* [MXS-1714](https://jira.mariadb.org/browse/MXS-1714) local_address is not used by internal connections
|
||||
* [MXS-1713](https://jira.mariadb.org/browse/MXS-1713) SchemaRouter unable to process SHOW DATABASES for a lot of schemas
|
||||
* [MXS-1705](https://jira.mariadb.org/browse/MXS-1705) Maxscale 2.2.2 crashes on startup with CentOS 7
|
||||
* [MXS-1701](https://jira.mariadb.org/browse/MXS-1701) Source building instructions are not correct
|
||||
* [MXS-1689](https://jira.mariadb.org/browse/MXS-1689) Error message in case both port and socket are defined is not clear
|
||||
* [MXS-1679](https://jira.mariadb.org/browse/MXS-1679) Maxscale does not detect failover executed by another Maxscale in 2 Maxscales + keepalived configuration
|
||||
|
||||
## 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).
|
||||
@ -1,78 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.5 Release Notes -- 2018-04-25
|
||||
|
||||
Release 2.2.5 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.5, when compared to
|
||||
release 2.2.4.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
* Info level messages will now also be logged to syslog, if logging to
|
||||
syslog is enabled.
|
||||
|
||||
## Dropped Features
|
||||
|
||||
## New Features
|
||||
|
||||
* The user can define custom SQL queries which are executed during switchover,
|
||||
failover and rejoin. See [MariaDB Monitor documentation](../Monitors/MariaDB-Monitor.md)
|
||||
for more information.
|
||||
|
||||
### MaxCtrl: Raw REST API Calls
|
||||
|
||||
MaxCtrl is now able to perform raw HTTP GET calls that return the JSON
|
||||
data from the REST API. It also supports value extraction with JavaScript
|
||||
style syntax.
|
||||
|
||||
For example, extracting just the state of all servers as a JSON array can be
|
||||
done with the following command:
|
||||
|
||||
```
|
||||
[markusjm@localhost ~]$ maxctrl api get servers data[].attributes.state
|
||||
["Master, Running","Slave, Running","Slave, Running","Slave, Running"]
|
||||
```
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1819](https://jira.mariadb.org/browse/MXS-1819) log_info does not log to syslog
|
||||
* [MXS-1815](https://jira.mariadb.org/browse/MXS-1815) threads=auto doesn't work as documented
|
||||
* [MXS-1814](https://jira.mariadb.org/browse/MXS-1814) Log warning when log_debug is used with release packages
|
||||
* [MXS-1808](https://jira.mariadb.org/browse/MXS-1808) COM_STMT_SEND_LONG_DATA lead to crash
|
||||
* [MXS-1807](https://jira.mariadb.org/browse/MXS-1807) Module command domains are case sensitive
|
||||
* [MXS-1805](https://jira.mariadb.org/browse/MXS-1805) MaxScale may hang with multiple concurrent maxadmin calls.
|
||||
* [MXS-1803](https://jira.mariadb.org/browse/MXS-1803) MaxScale docker image does not work
|
||||
* [MXS-1787](https://jira.mariadb.org/browse/MXS-1787) Crash with mysql client test `test_bug49972`
|
||||
* [MXS-1786](https://jira.mariadb.org/browse/MXS-1786) Hang with COM_STATISTICS
|
||||
* [MXS-1785](https://jira.mariadb.org/browse/MXS-1785) request 16M-1 normal sql + 'select 1' core dump with debug mode
|
||||
* [MXS-1776](https://jira.mariadb.org/browse/MXS-1776) Hang with mysql test case `test_basic_cursors`
|
||||
* [MXS-1773](https://jira.mariadb.org/browse/MXS-1773) LOAD DATA LOCAL INFILE confuses readwritesplit
|
||||
* [MXS-1765](https://jira.mariadb.org/browse/MXS-1765) Internal client connections write data in wrong order
|
||||
* [MXS-1757](https://jira.mariadb.org/browse/MXS-1757) Problem while linking libavrorouter.so on Ubuntu 14.04
|
||||
* [MXS-1751](https://jira.mariadb.org/browse/MXS-1751) Maxscale crashes when certain config is in play (with nodes down)
|
||||
* [MXS-1747](https://jira.mariadb.org/browse/MXS-1747) Rejoin functions should print better errors
|
||||
* [MXS-1746](https://jira.mariadb.org/browse/MXS-1746) The session-specific gtid_domain_id is queried instead of the global one
|
||||
* [MXS-1743](https://jira.mariadb.org/browse/MXS-1743) Maxscale unable to enforce round-robin between read service for Slave
|
||||
* [MXS-1618](https://jira.mariadb.org/browse/MXS-1618) Maxadmin Binary Hangs on a Big endian Platform
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,57 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.6 Release Notes -- 2018-05-21
|
||||
|
||||
Release 2.2.6 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.6, when compared to
|
||||
release 2.2.5.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## New Features
|
||||
|
||||
* It is now possible to configure the MariaDB Monitor to turn
|
||||
on the read_only flag of a server it deems is a slave.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1874](https://jira.mariadb.org/browse/MXS-1874) SET STATEMENT ... FOR is wrongly classified
|
||||
* [MXS-1873](https://jira.mariadb.org/browse/MXS-1873) Errors with large session commands
|
||||
* [MXS-1866](https://jira.mariadb.org/browse/MXS-1866) Prepared statements do not work
|
||||
* [MXS-1861](https://jira.mariadb.org/browse/MXS-1861) masking filter logs warnings with multistatements
|
||||
* [MXS-1852](https://jira.mariadb.org/browse/MXS-1852) mysql_client_test test_bug17309863 failed
|
||||
* [MXS-1847](https://jira.mariadb.org/browse/MXS-1847) Race condition in server_get_parameter
|
||||
* [MXS-1846](https://jira.mariadb.org/browse/MXS-1846) Wrong packet number in KILL command error
|
||||
* [MXS-1843](https://jira.mariadb.org/browse/MXS-1843) Sporadic test_logthrottling failures on Ubuntu
|
||||
* [MXS-1839](https://jira.mariadb.org/browse/MXS-1839) show sessions leaks memory
|
||||
* [MXS-1837](https://jira.mariadb.org/browse/MXS-1837) Typo in REST API service stop documentation
|
||||
* [MXS-1836](https://jira.mariadb.org/browse/MXS-1836) MaxInfo show eventTimes returns garbage.
|
||||
* [MXS-1833](https://jira.mariadb.org/browse/MXS-1833) Connection timeout when creating CONNECT tables for maxinfo in Galera cluster with SSL set up
|
||||
* [MXS-1832](https://jira.mariadb.org/browse/MXS-1832) maxctrl returns 0 even when errors are returned
|
||||
* [MXS-1831](https://jira.mariadb.org/browse/MXS-1831) No error on invalid monitor parameter alteration
|
||||
* [MXS-1830](https://jira.mariadb.org/browse/MXS-1830) Invalid free in Cache test program
|
||||
* [MXS-1829](https://jira.mariadb.org/browse/MXS-1829) SELECT PREVIOUS VALUE FOR SEC classified differently than SELECT NEXT...
|
||||
* [MXS-1826](https://jira.mariadb.org/browse/MXS-1826) COM_CHANGE_USER not work with Oracle MySQL
|
||||
* [MXS-1825](https://jira.mariadb.org/browse/MXS-1825) test_wl4435_3 case from mysql_client_test.c lead to crash
|
||||
* [MXS-1824](https://jira.mariadb.org/browse/MXS-1824) test_bug11909 case from mysql_client_test.c lead to crash
|
||||
* [MXS-1772](https://jira.mariadb.org/browse/MXS-1772) Netmask limitations are not documented
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,36 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.7 Release Notes -- 2018-05-29
|
||||
|
||||
Release 2.2.7 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.7, when compared to
|
||||
release 2.2.6.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1882](https://jira.mariadb.org/browse/MXS-1882) Maxscale don't recognize logdir= in /etc/maxscale.cnf.d/maxscale.cnf
|
||||
* [MXS-1879](https://jira.mariadb.org/browse/MXS-1879) use_priorities is missed out of show monitor command
|
||||
* [MXS-1878](https://jira.mariadb.org/browse/MXS-1878) Worker post fails due to: Resource temporarily unavailable
|
||||
* [MXS-1875](https://jira.mariadb.org/browse/MXS-1875) MaxScale crashes 5 minutes after OS startup
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,34 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.8 Release Notes -- Not Released
|
||||
|
||||
Release 2.2.8 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.8, when compared to
|
||||
release 2.2.7.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
* [MXS-1889](https://jira.mariadb.org/browse/MXS-1889) A single remaining master is valid for readconnroute configured with 'router_options=slave'
|
||||
* [MXS-1740](https://jira.mariadb.org/browse/MXS-1740) Hintfilter leaks memory
|
||||
|
||||
## 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/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 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).
|
||||
@ -1,40 +0,0 @@
|
||||
# MariaDB MaxScale 2.2.9 Release Notes -- 2018-06-06
|
||||
|
||||
Release 2.2.9 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.2.9, when compared to
|
||||
release 2.2.7 (2.2.8 was not officially released).
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
### 2.2.9
|
||||
* [MXS-1899](https://jira.mariadb.org/browse/MXS-1899) generated [maxscale] section causes errors
|
||||
* [MXS-1896](https://jira.mariadb.org/browse/MXS-1896) LOAD DATA INFILE is mistaken for LOAD DATA LOCAL INFILE
|
||||
* [MXS-1743](https://jira.mariadb.org/browse/MXS-1743) Maxscale unable to enforce round-robin between read service for Slave
|
||||
|
||||
### 2.2.8
|
||||
* [MXS-1889](https://jira.mariadb.org/browse/MXS-1889) A single remaining master is valid for readconnroute configured with 'router_options=slave'
|
||||
* [MXS-1740](https://jira.mariadb.org/browse/MXS-1740) Hintfilter leaks memory
|
||||
|
||||
## 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/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 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).
|
||||
Loading…
x
Reference in New Issue
Block a user