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

Update released notes

Browse Source 
MXS-621 fix removed. Too complex in current timeframe.
This commit is contained in:
Johan Wikman 2016-04-26 13:45:32 +03:00
parent cc90c24340
commit 9c8e39262b
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md
View File

@ -21,8 +21,7 @@ report at [Jira](https://jira.mariadb.org).
* [MXS-662](https://jira.mariadb.org/browse/MXS-662): No Listener on different IPs but same port since 1.4.0
* [MXS-661](https://jira.mariadb.org/browse/MXS-661): Log fills with 'Length (0) is 0 or query string allocation failed'
* [MXS-656](https://jira.mariadb.org/browse/MXS-656): after upgrade from 1.3 to 1.4, selecting master isn't working as expected
* [MXS-621](https://jira.mariadb.org/browse/MXS-621): MaxScale fails to start silently if config file is not readable
* [MXS-616](https://jira.mariadb.org/browse/MXS-616): Duplicated binlog event under head load.
* [MXS-616](https://jira.mariadb.org/browse/MXS-616): Duplicated binlog event under heavy load.
## Known Issues and Limitations