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

Merge branch '2.3' into develop

Browse Source
This commit is contained in:
Markus Mäkelä
2019-04-23 12:05:18 +03:00
parent 9e3f0aab5a ba79028a46
commit 4186f39616
26 changed files with 134 additions and 78 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1,4 +1,4 @@
# MariaDB MaxScale 2.3.6 Release Notes
# MariaDB MaxScale 2.3.6 Release Notes -- 2019-04-23
Release 2.3.6 is a GA release.
@ -11,6 +11,7 @@ report on [our Jira](https://jira.mariadb.org/projects/MXS).
## New Features
* [MXS-2417](https://jira.mariadb.org/browse/MXS-2417) MaxScale main config should take precedence over runtime config on restart
* [MXS-2344](https://jira.mariadb.org/browse/MXS-2344) Support MASTER_SSL in mariadbmon for encrypting replication traffic
### REST API & MaxCtrl: Hard maintenance mode
@ -24,8 +25,12 @@ the `set` endpoint.
## Bug fixes
* [MXS-2423](https://jira.mariadb.org/browse/MXS-2423) retain_last_statements not in maxctrl show maxscale
* [MXS-2419](https://jira.mariadb.org/browse/MXS-2419) Hangs on query during multiple transaction replays
* [MXS-2418](https://jira.mariadb.org/browse/MXS-2418) Crash on transaction replay if log_info is on and session starts with no master
* [MXS-2416](https://jira.mariadb.org/browse/MXS-2416) Possible memory leak
* [MXS-2324](https://jira.mariadb.org/browse/MXS-2324) Maxscale disconnect after commit without begin from Icinga2
* [MXS-2259](https://jira.mariadb.org/browse/MXS-2259) Maxscale consumes large amounts of memory even with buffer limits set.
## Known Issues and Limitations