Merge branch '2.0' into develop
This commit is contained in:
Johan Wikman
@ -126,4 +126,4 @@ 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-bsl).
|
||||
The source code is available [here](https://github.com/mariadb-corporation/MaxScale).
|
||||
|
||||
130
Documentation/Release-Notes/MaxScale-2.0.1-Release-Notes.md
Normal file
130
Documentation/Release-Notes/MaxScale-2.0.1-Release-Notes.md
Normal file
@ -0,0 +1,130 @@
|
||||
# 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).
|
||||
|
||||
## 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.1.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20in%20(2.0.0%2C%202.0.1)%20AND%20resolved%20%3E%3D%20-21d%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC)
|
||||
|
||||
* [MXS-847](https://jira.mariadb.org/browse/MXS-847): server_down event is executed 8 times due to putting sever into maintenance mode
|
||||
* [MXS-845](https://jira.mariadb.org/browse/MXS-845): "Server down" event is re-triggered after maintenance mode is repeated
|
||||
* [MXS-842](https://jira.mariadb.org/browse/MXS-842): Unexpected / undocumented behaviour when multiple available masters from mmmon monitor
|
||||
* [MXS-846](https://jira.mariadb.org/browse/MXS-846): MMMon: Maintenance mode on slave logs error message every second
|
||||
|
||||
## 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 maxscale-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).
|
||||
Reference in New Issue
Block a user