From 9c8e39262bfec6cf8fcc847a82be8ca7b55700ea Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Tue, 26 Apr 2016 13:45:32 +0300 Subject: [PATCH] Update released notes MXS-621 fix removed. Too complex in current timeframe. --- Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md b/Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md index 1eb1299ac..3954cd770 100644 --- a/Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-1.4.2-Release-Notes.md @@ -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