Remove all but 2.1 release notes from 2.1 branch
This commit is contained in:
Johan Wikman
parent
f350b58509
commit
6868c87598
@ -1,129 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.0 Release Notes
|
||||
|
||||
Release 2.0.0 is a Beta release.
|
||||
|
||||
This document describes the changes in release 2.0.0, when compared to
|
||||
release 1.4.3.
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## License
|
||||
|
||||
The license of MaxScale has been changed from GPLv2 to MariaDB BSL.
|
||||
|
||||
For more information about MariaDB BSL, please refer to
|
||||
[MariaDB BSL](https://www.mariadb.com/bsl).
|
||||
|
||||
## New Features
|
||||
|
||||
### Binlog-to-Avro Translator
|
||||
|
||||
The 2.0 release of MaxScale contains the beta release of the binlog-to-Avro
|
||||
conversion and distribution modules. These modules allow MaxScale to connect to
|
||||
a MariaDB 10.0 master server and convert the binary log events to Avro format
|
||||
change records. These records can then be queries as a continuous JSON or raw Avro
|
||||
stream using the new CDC protocol.
|
||||
|
||||
The [Avrorouter Tutorial](../Tutorials/Avrorouter-Tutorial.md) contains
|
||||
information on how to get started with the binlog-to-Avro translation.
|
||||
|
||||
The [Avrorouter](../Routers/Avrorouter.md) documentation has more information
|
||||
on the details of this conversion process and how to configure the module.
|
||||
|
||||
The [CDC Protocol](../Protocols/CDC.md) documentation contains the details of
|
||||
the new protocol.
|
||||
|
||||
### Read Continuation upon Master Down
|
||||
|
||||
The _readwritesplit_ routing module now supports a high availability read mode
|
||||
where read queries are allowed even if the master server goes down. The new
|
||||
functionality supports three modes: disconnection on master failure, disconnection
|
||||
on first write after master failure and error on write after master failure.
|
||||
|
||||
The MySQL monitor module, _mysqlmon_, now supports stale states for both the master
|
||||
and slave servers. This means that when a slave loses its master, it will retain
|
||||
the slave state as long as it is running.
|
||||
|
||||
For more details about these new modes, please read the [ReadWriteSplit](../Routers/ReadWriteSplit.md)
|
||||
and [MySQL Monitor](../Monitors/MySQL-Monitor.md) documentation.
|
||||
|
||||
### Backend SSL
|
||||
|
||||
The configuration for a backend server can now be set for SSL connections from MaxScale. Although loosely referred to as SSL, this is nowadays the TLS security protocol. If, in MaxScale, a server is configured with SSL parameters then MaxScale will only connect to it using a secure protocol. MaxScale supports TLS versions 1.0, 1.1 and 1.2; which can be used will depend on the capability of the backend server. Once configured, if a secure connection cannot be made, attempts to connect to MaxScale that require that server will fail. An alternative that should be considered is the use of SSH tunnels.
|
||||
|
||||
For more information about backend SSL, please refer to
|
||||
[Server and SSL](../Getting-Started/Configuration-Guide.md#server-and-ssl)
|
||||
|
||||
### Connection Throttling
|
||||
|
||||
The option now exists to set [max_connections](../Getting-Started/Configuration-Guide.md#max_connections) for a service. If a non-zero number is specified, then MaxScale will accept connection requests only up to the specified limit. Further connections will receive the error message "Too many connections" with error number 1040. .
|
||||
|
||||
### MaxAdmin Security Improvements
|
||||
|
||||
The way a user of MaxAdmin is authenticated has been completely changed.
|
||||
In 2.0, MaxAdmin can only connect to MaxScale using a domain socket, thus
|
||||
_only when run on the same host_, and authorization is based upon the UNIX
|
||||
identity. Remote access is no longer supported.
|
||||
|
||||
When 2.0 has been installed, MaxAdmin can only be used by `root` and
|
||||
other users must be added anew. Please consult
|
||||
[MaxAdmin documentation](../Reference/MaxAdmin.md) for more details.
|
||||
|
||||
### Query Classifier
|
||||
|
||||
The query classifier component that MaxScale uses when deciding what
|
||||
to do with a particular query has been changed. It used to be based
|
||||
upon the MariaDB embedded library, but is now based upon sqlite3.
|
||||
This change should not cause any changes in the behaviour of MaxScale.
|
||||
|
||||
For more information, please refer to
|
||||
[Configuration Guide](../Getting-Started/Configuration-Guide.md#query_classifier).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed since the release of MaxScale 1.4.3.](https://jira.mariadb.org/browse/MXS-739?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20resolution%20in%20(Fixed%2C%20Done)%20AND%20fixVersion%20%3D%202.0.0)
|
||||
|
||||
* [MXS-821](https://jira.mariadb.org/browse/MXS-821): filestem router option for binlog router is not documented
|
||||
* [MXS-814](https://jira.mariadb.org/browse/MXS-814): Service and monitor permission checks only use the last available server
|
||||
* [MXS-813](https://jira.mariadb.org/browse/MXS-813): binlogrouter, mariadb10.0, signal 11, crash
|
||||
* [MXS-801](https://jira.mariadb.org/browse/MXS-801): strip_db_esc should default to True
|
||||
* [MXS-790](https://jira.mariadb.org/browse/MXS-790): replication_heartbeat table privilege is not checked / fails silently / is not documented
|
||||
* [MXS-776](https://jira.mariadb.org/browse/MXS-776): Documentation about limitations of reload config is not clear
|
||||
* [MXS-772](https://jira.mariadb.org/browse/MXS-772): RPM installation produces errors
|
||||
* [MXS-766](https://jira.mariadb.org/browse/MXS-766): R/W router sends DEALLOCATE PREPARE to ALL instead of MASTER
|
||||
* [MXS-739](https://jira.mariadb.org/browse/MXS-739): Maxinfo issuing invalid null's in JSON response
|
||||
* [MXS-733](https://jira.mariadb.org/browse/MXS-733): MaxScale `list sessions` can report "Invalid State" for some sessions.
|
||||
* [MXS-720](https://jira.mariadb.org/browse/MXS-720): MaxScale fails to start and doesn't log any useful message when there are spurious characters in the config file
|
||||
* [MXS-718](https://jira.mariadb.org/browse/MXS-718): qc_mysqlembedded does not report fields for INSERT
|
||||
* [MXS-704](https://jira.mariadb.org/browse/MXS-704): start/stop scripts use which in a non-silent manner
|
||||
* [MXS-695](https://jira.mariadb.org/browse/MXS-695): MaxScale does not build on Debian 8 following build from source instructions
|
||||
* [MXS-685](https://jira.mariadb.org/browse/MXS-685): 1.4.1: ReadWrite Split on Master-Master setup doesn't chose master, logs "RUNNING MASTER" error message instead (related to MXS-511?)
|
||||
* [MXS-675](https://jira.mariadb.org/browse/MXS-675): QLA Filter Output Log Improvements
|
||||
* [MXS-658](https://jira.mariadb.org/browse/MXS-658): Crash in embedded library when MariaDB 10.0 is used
|
||||
* [MXS-653](https://jira.mariadb.org/browse/MXS-653): maxpasswd writes notice message to stdout
|
||||
* [MXS-652](https://jira.mariadb.org/browse/MXS-652): ssl is configured in a wrong way, but Maxscale can be started and works
|
||||
* [MXS-633](https://jira.mariadb.org/browse/MXS-633): Galera Monitor should not require the REPLICATION CLIENT privilege
|
||||
* [MXS-631](https://jira.mariadb.org/browse/MXS-631): Rename and clean up macros.cmake
|
||||
* [MXS-477](https://jira.mariadb.org/browse/MXS-477): readconnroute misinterprets data as COM_CHANGE_USER
|
||||
* [MXS-419](https://jira.mariadb.org/browse/MXS-419): Socket creation failed due 24, Too many open files.
|
||||
|
||||
## 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,146 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.1 Release Notes
|
||||
|
||||
Release 2.0.1 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.0.1, when compared to
|
||||
[release 2.0.0](MaxScale-2.0.0-Release-Notes.md).
|
||||
|
||||
If you are upgrading from 1.4.3, please also read the release notes
|
||||
of [2.0.0](./MaxScale-2.0.0-Release-Notes.md).
|
||||
|
||||
For any problems you encounter, please consider submitting a bug
|
||||
report at [Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed default values
|
||||
|
||||
### `strip_db_esc`
|
||||
|
||||
The service parameter [_strip_db_esc_](../Getting-Started/Configuration-Guide.md#strip_db_esc)
|
||||
now defaults to true.
|
||||
|
||||
### `detect_stale_master`
|
||||
|
||||
The [stale master detection](../Monitors/MySQL-Monitor.md#detect_stale_master)
|
||||
feature is now enabled by default.
|
||||
|
||||
## Updated Features
|
||||
|
||||
### Starting MariaDB MaxScale
|
||||
|
||||
There is now a new command line parameter `--basedir=PATH` that will
|
||||
cause all directory paths and the location of the configuration file
|
||||
to be defined relative to that path.
|
||||
|
||||
For instance, invoking MariaDB MaxScale like
|
||||
|
||||
$ maxscale --basedir=/path/maxscale
|
||||
|
||||
has the same effect as invoking MariaDB MaxScale like
|
||||
|
||||
$ maxscale --config=/path/maxscale/etc/maxscale.cnf
|
||||
--configdir=/path/maxscale/etc
|
||||
--logdir=/path/maxscale/var/log/maxscale
|
||||
--cachhedir=/path/maxscale/var/cache/maxscale
|
||||
--libdir=/path/maxscale/lib/maxscale
|
||||
--datadir=/path/maxscale/var/lib/maxscale
|
||||
--execdir=/path/maxscale/bin
|
||||
--language=/path/maxscale/var/lib/maxscale
|
||||
--piddir=/path/maxscale/var/run/maxscale
|
||||
|
||||
### Password parameter
|
||||
|
||||
In the configuration entry for a _service_ or _monitor_, the value of
|
||||
the password to be used can now be specified using `password` in addition
|
||||
to `passwd`. The use of the latter will be deprecated and removed in later
|
||||
releases of MaxScale.
|
||||
|
||||
[SomeService]
|
||||
...
|
||||
password=mypasswd
|
||||
|
||||
### Routing hint priority change
|
||||
|
||||
Routing hints now have the highest priority when a routing decision is made. If
|
||||
there is a conflict between the original routing decision made by the
|
||||
readwritesplit and the routing hint attached to the query, the routing hint
|
||||
takes higher priority.
|
||||
|
||||
What this change means is that, if a query would normally be routed to the
|
||||
master but the routing hint instructs the router to route it to the slave, it
|
||||
would be routed to the slave.
|
||||
|
||||
**WARNING**: This change can alter the way some statements are routed and could
|
||||
possibly cause data loss, corruption or inconsisteny. Please consult the [Hint
|
||||
Syntax](../Reference/Hint-Syntax.md) and
|
||||
[ReadWriteSplit](../Routers/ReadWriteSplit.md) documentation before using
|
||||
routing hints.
|
||||
|
||||
### MaxAdmin Usage
|
||||
|
||||
In 2.0.0 (Beta), the authentication mechanism of MaxAdmin was completely
|
||||
changed, so that MaxAdmin could only connect to MaxScale using a Unix domain
|
||||
socket, thus _only when run on the same host_, and authorization was based
|
||||
on the Unix identity. Remote access was no longer supported.
|
||||
|
||||
To the user this was visible so that while you in 1.4.3 had to provide
|
||||
a password when starting _maxadmin_ and when adding a user
|
||||
```
|
||||
user@host $ maxadmin -p password
|
||||
MaxAdmin> add user john johns-password
|
||||
```
|
||||
in 2.0.0 (Beta), where only Unix domain sockets could be used, you did not
|
||||
have to provide a password neither when starting _maxadmin_, nor when adding
|
||||
users
|
||||
```
|
||||
user@host $ maxadmin
|
||||
MaxAdmin> add user john
|
||||
```
|
||||
as the MaxScale user corresponded to a Unix user, provided the Linux user
|
||||
had been added as a user of MaxScale.
|
||||
|
||||
In 2.0.1 (GA) this has been changed so that the 1.4.3 behaviour is intact
|
||||
but _deprecated_, and the 2.0.0 (Beta) behaviour is exposed using a new set
|
||||
of commands:
|
||||
```
|
||||
MaxAdmin> enable account alice
|
||||
MaxAdmin> disable account alice
|
||||
```
|
||||
Note that the way you need to invoke _maxadmin_ depends upon how MariaDB
|
||||
MaxScale has been configued.
|
||||
|
||||
Please consult
|
||||
[MaxAdmin documentation](../Reference/MaxAdmin.md) for more details.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed since the release of MaxScale 2.0.0.](https://jira.mariadb.org/browse/MXS-860?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20in%20(2.0.1)%20AND%20resolved%20%3E%3D%20-21d%20AND%20(resolution%20%3D%20Done%20OR%20resolution%20%3D%20Fixed)%20ORDER%20BY%20priority%20DESC)
|
||||
|
||||
* [MXS-860](https://jira.mariadb.org/browse/MXS-860): I want to access the web site if master server is down
|
||||
* [MXS-870](https://jira.mariadb.org/browse/MXS-870): Assertion of Buffer Overflow
|
||||
* [MXS-845](https://jira.mariadb.org/browse/MXS-845): "Server down" event is re-triggered after maintenance mode is repeated
|
||||
* [MXS-836](https://jira.mariadb.org/browse/MXS-836): "Failed to start all MaxScale services" without retrying
|
||||
* [MXS-835](https://jira.mariadb.org/browse/MXS-835): Please reinstate remote access to maxscaled protocol
|
||||
* [MXS-773](https://jira.mariadb.org/browse/MXS-773): 100% CPU on idle MaxScale with MaxInfo
|
||||
* [MXS-812](https://jira.mariadb.org/browse/MXS-812): Number of conns not matching number of operations
|
||||
* [MXS-856](https://jira.mariadb.org/browse/MXS-856): If config file cannot be accessed and creation of log file fails, MaxScale crashes with SIGSEGV
|
||||
* [MXS-829](https://jira.mariadb.org/browse/MXS-829): When the config file isn't readable or doesn't exist, maxscale silently ends
|
||||
|
||||
## 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 derived
|
||||
from the version of MaxScale. For instance, the tag of version `X.Y.Z` of MaxScale
|
||||
is `maxscale-X.Y.Z`.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
@ -1,64 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.2 Release Notes
|
||||
|
||||
Release 2.0.2 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.0.2, when compared to
|
||||
release [2.0.1](MaxScale-2.0.1-Release-Notes.md).
|
||||
|
||||
If you are upgrading from release 1.4.4, please also read the release
|
||||
notes of release [2.0.0](./MaxScale-2.0.0-Release-Notes.md) and
|
||||
release [2.0.1](./MaxScale-2.0.1-Release-Notes.md).
|
||||
|
||||
For any problems you encounter, please submit a bug report at
|
||||
[Jira](https://jira.mariadb.org).
|
||||
|
||||
## Updated Features
|
||||
|
||||
### [MXS-978] (https://jira.mariadb.org/browse/MXS-978) Support for stale master in case of restart
|
||||
|
||||
In case where replication monitor gets a stale master status (slaves are down)
|
||||
and maxscale gets restarted, master loses the stale master status and no writes
|
||||
can happen.
|
||||
|
||||
To cater for this situation there is now a `set server <name> stale` command.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here is a list of bugs fixed since the release of MaxScale 2.0.1.](https://jira.mariadb.org/browse/MXS-976?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.0.2)
|
||||
|
||||
* [MXS-1018](https://jira.mariadb.org/browse/MXS-1018): Internal connections don't use TLS
|
||||
* [MXS-1008](https://jira.mariadb.org/browse/MXS-1008): MySQL Monitor with scripts leaks memory
|
||||
* [MXS-976](https://jira.mariadb.org/browse/MXS-976): Crash in libqc_sqlite
|
||||
* [MXS-975](https://jira.mariadb.org/browse/MXS-975): TCP backlog is capped at 1280
|
||||
* [MXS-970](https://jira.mariadb.org/browse/MXS-970): A fatal problem with maxscale automatically shut down
|
||||
* [MXS-969](https://jira.mariadb.org/browse/MXS-969): use_sql_variables_in=master can break functionality of important session variables
|
||||
* [MXS-967](https://jira.mariadb.org/browse/MXS-967): setting connection_timeout=value cause error : Not a boolean value
|
||||
* [MXS-965](https://jira.mariadb.org/browse/MXS-965): galeramon erlaubt keine TLS verschlüsselte Verbindung
|
||||
* [MXS-960](https://jira.mariadb.org/browse/MXS-960): MaxScale Binlog Server does not allow comma to be in password
|
||||
* [MXS-957](https://jira.mariadb.org/browse/MXS-957): Temporary table creation from another temporary table isn't detected
|
||||
* [MXS-956](https://jira.mariadb.org/browse/MXS-956): Removing DCB 0x7fbf94016760 but was in state DCB_STATE_DISCONNECTED which is not legal for a call to dcb_close
|
||||
* [MXS-955](https://jira.mariadb.org/browse/MXS-955): MaxScale 2.0.1 doesn't recognize user and passwd options in .maxadmin file
|
||||
* [MXS-953](https://jira.mariadb.org/browse/MXS-953): Charset error when server configued in utf8mb4
|
||||
* [MXS-942](https://jira.mariadb.org/browse/MXS-942): describe table query not routed to shard that contains the schema
|
||||
* [MXS-917](https://jira.mariadb.org/browse/MXS-917): False error message about master not being in use
|
||||
|
||||
## 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 derived
|
||||
from the version of MaxScale. For instance, the tag of version `X.Y.Z` of MaxScale
|
||||
is `maxscale-X.Y.Z`.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
|
||||
@ -1,57 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.3 Release Notes
|
||||
|
||||
Release 2.0.3 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.0.3, when compared to
|
||||
release [2.0.2](MaxScale-2.0.2-Release-Notes.md).
|
||||
|
||||
If you are upgrading from release 1.4.4, please also read the release
|
||||
notes of release [2.0.0](./MaxScale-2.0.0-Release-Notes.md),
|
||||
release [2.0.1](./MaxScale-2.0.1-Release-Notes.md) and
|
||||
release [2.0.2](./MaxScale-2.0.2-Release-Notes.md).
|
||||
|
||||
For any problems you encounter, please submit a bug report at
|
||||
[Jira](https://jira.mariadb.org).
|
||||
|
||||
## Updated Features
|
||||
|
||||
### [MXS-1027] (https://jira.mariadb.org/browse/MXS-1027) Add Upstart support (including respawn) for MaxScale
|
||||
|
||||
MaxScale now provides an Upstart configuration file for systems that do not
|
||||
support systemd.
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here](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.0.3)
|
||||
is a list of bugs fixed since the release of MaxScale 2.0.2.
|
||||
|
||||
* [MXS-1048](https://jira.mariadb.org/browse/MXS-1048): ShemaRouter can't handle backquoted database names
|
||||
* [MXS-1047](https://jira.mariadb.org/browse/MXS-1047): Batch inserts through Maxscale with C/J stall
|
||||
* [MXS-1045](https://jira.mariadb.org/browse/MXS-1045): Defunct processes after maxscale have executed script during failover
|
||||
* [MXS-1044](https://jira.mariadb.org/browse/MXS-1044): Init-Script for SLES 11 displays error messages when called
|
||||
* [MXS-1043](https://jira.mariadb.org/browse/MXS-1043): Reading last insert id from @@identity variable does not work with maxscale
|
||||
* [MXS-1033](https://jira.mariadb.org/browse/MXS-1033): maxscale crushes on maxadmin request
|
||||
* [MXS-1026](https://jira.mariadb.org/browse/MXS-1026): Crash with NullAuth authenticator
|
||||
* [MXS-1009](https://jira.mariadb.org/browse/MXS-1009): maxinfo sigsegv in spinlock_release
|
||||
* [MXS-964](https://jira.mariadb.org/browse/MXS-964): Fatal: MaxScale 2.0.1 received fatal signal 6
|
||||
* [MXS-956](https://jira.mariadb.org/browse/MXS-956): Maxscale crash: Removing DCB 0x7fbf94016760 but was in state DCB_STATE_DISCONNECTED which is not legal for a call to dcb_close
|
||||
|
||||
## 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 derived
|
||||
from the version of MaxScale. For instance, the tag of version `X.Y.Z` of MaxScale
|
||||
is `maxscale-X.Y.Z`.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
@ -1,57 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.4 Release Notes -- 2017-02-01
|
||||
|
||||
Release 2.0.4 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.0.4, when compared to
|
||||
release [2.0.3](MaxScale-2.0.3-Release-Notes.md).
|
||||
|
||||
If you are upgrading from release 1.4, please also read the release
|
||||
notes of release [2.0.3](./MaxScale-2.0.3-Release-Notes.md),
|
||||
release [2.0.2](./MaxScale-2.0.2-Release-Notes.md),
|
||||
release [2.0.1](./MaxScale-2.0.1-Release-Notes.md) and
|
||||
[2.0.0](./MaxScale-2.0.0-Release-Notes.md).
|
||||
|
||||
For any problems you encounter, please submit a bug report at
|
||||
[Jira](https://jira.mariadb.org).
|
||||
|
||||
## Changed Features
|
||||
|
||||
- The dbfwfilter now rejects all prepared statements instead of ignoring
|
||||
them. This affects _wildcard_, _columns_, _on_queries_ and _no_where_clause_
|
||||
type rules which previously ignored prepared statements.
|
||||
|
||||
- The dbfwfilter now allows COM_PING and other commands though when
|
||||
`action=allow`. See [../Filters/Database-Firewall-Filter.md](documentation)
|
||||
for more details.
|
||||
|
||||
- The MariaDB Connector-C was upgraded to a preliminary release of version 2.3.3 (fixes MXS-951).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here](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.0.4)
|
||||
is a list of bugs fixed since the release of MaxScale 2.0.3.
|
||||
|
||||
* [MXS-1111](https://jira.mariadb.org/browse/MXS-1111): Request Ping not allowed
|
||||
* [MXS-1082](https://jira.mariadb.org/browse/MXS-1082): Block prepared statements
|
||||
* [MXS-1080](https://jira.mariadb.org/browse/MXS-1080): Readwritesplit (documentation of max_slave_replication_lag)
|
||||
* [MXS-951](https://jira.mariadb.org/browse/MXS-951): Using utf8mb4 on galera hosts stops maxscale connections
|
||||
|
||||
## 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 derived
|
||||
from the version of MaxScale. For instance, the tag of version `X.Y.Z` of MaxScale
|
||||
is `maxscale-X.Y.Z`.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
@ -1,47 +0,0 @@
|
||||
# MariaDB MaxScale 2.0.5 Release Notes
|
||||
|
||||
Release 2.0.5 is a GA release.
|
||||
|
||||
This document describes the changes in release 2.0.5, when compared to
|
||||
release [2.0.4](MaxScale-2.0.4-Release-Notes.md).
|
||||
|
||||
If you are upgrading from release 1.4, please also read the following
|
||||
release notes:
|
||||
[2.0.4](./MaxScale-2.0.4-Release-Notes.md),
|
||||
[2.0.3](./MaxScale-2.0.3-Release-Notes.md),
|
||||
[2.0.2](./MaxScale-2.0.2-Release-Notes.md),
|
||||
[2.0.1](./MaxScale-2.0.1-Release-Notes.md) and
|
||||
[2.0.0](./MaxScale-2.0.0-Release-Notes.md).
|
||||
|
||||
For any problems you encounter, please submit a bug report at
|
||||
[Jira](https://jira.mariadb.org).
|
||||
|
||||
## Bug fixes
|
||||
|
||||
[Here](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.0.5)
|
||||
is a list of bugs fixed since the release of MaxScale 2.0.4.
|
||||
|
||||
* [MXS-1130](https://jira.mariadb.org/browse/MXS-1130): Unexpected length encoding 'ff' encountered
|
||||
* [MXS-1123](https://jira.mariadb.org/browse/MXS-1123): connect_timeout setting causes frequent disconnects
|
||||
* [MXS-1081](https://jira.mariadb.org/browse/MXS-1081): Avro data file corruption
|
||||
* [MXS-1025](https://jira.mariadb.org/browse/MXS-1025): qc_sqlite always reports " Statement was parsed, but not classified"
|
||||
|
||||
## 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 derived
|
||||
from the version of MaxScale. For instance, the tag of version `X.Y.Z` of MaxScale
|
||||
is `maxscale-X.Y.Z`.
|
||||
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
Loading…
x
Reference in New Issue
Block a user