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

Update 2.2 ChangeLog, Release notes, and Upgrading doc.

Browse Source
This commit is contained in:
Johan Wikman 2017-12-19 13:58:15 +02:00
parent 7813be0972
commit 3e398004e8
3 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/Changelog.md
View File

@ -24,6 +24,8 @@
* KILL CONNECTION can now be used through MaxScale.
* Environment variables can now be used in the MaxScale configuration file.
* By default, MaxScale can no longer be run as root.
* The MySQL Monitor is now capable of performing failover and switchover of
the master. There is also limited capability for rejoining nodes.
For more details, please refer to:
* [MariaDB MaxScale 2.2.0 Release Notes](Release-Notes/MaxScale-2.2.0-Release-Notes.md)

15
Documentation/Release-Notes/MaxScale-2.2.1-Release-Notes.md
View File

@ -46,6 +46,11 @@ been changed from `false` to `true`.
## New Features
### MySQL Monitor
Esa, add brief notes on failver, switchover and rejoin, with a link to the
actual documentation.
### REST API Relationship Endpoints
The _servers_, _monitors_ and _services_ types now support direct updating of
@ -84,6 +89,16 @@ for details.
[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-1545](https://jira.mariadb.org/browse/MXS-1545) Fix GTID connecting slave error detections
* [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.

3
Documentation/Upgrading/Upgrading-To-MaxScale-2.2.md
View File

@ -6,7 +6,8 @@ This document describes possible issues upgrading MariaDB MaxScale from version
For more information about MariaDB MaxScale 2.2, please refer to the
[ChangeLog](../Changelog.md).
For a complete list of changes in MaxScale 2.2.0, refer to the
For a complete list of changes in MaxScale 2.2, refer to the
[MaxScale 2.2.1 Release Notes](../Release-Notes/MaxScale-2.2.1-Release-Notes.md).
[MaxScale 2.2.0 Release Notes](../Release-Notes/MaxScale-2.2.0-Release-Notes.md).
Before starting the upgrade, we recommend you back up your current configuration