From 2b25f8522f51f98813ebb23e4dba0dab58e75c17 Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Wed, 28 Nov 2018 14:26:15 +0200 Subject: [PATCH 1/3] Update 2.3 changelog and 2.3.2 release notes --- Documentation/Changelog.md | 1 + .../Release-Notes/MaxScale-2.3.2-Release-Notes.md | 15 ++++++++++++++- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/Documentation/Changelog.md b/Documentation/Changelog.md index 57e0cb766..bcb618699 100644 --- a/Documentation/Changelog.md +++ b/Documentation/Changelog.md @@ -27,6 +27,7 @@ * The binlog router can now automatically switch to secondary masters when replicating from a Galera cluster in case the primary master goes down. +* MaxScale now has a systemd compatible watchdog. For more details, please refer to: diff --git a/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md index 6e0130955..d4e09dd78 100644 --- a/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md @@ -1,6 +1,6 @@ # MariaDB MaxScale 2.3.2 Release Notes -Release 2.3.2 is a XXX release. +Release 2.3.2 is a GA release. This document describes the changes in release 2.3.2, when compared to the previous release in the same series. @@ -33,8 +33,21 @@ output to "SHOW ALL SLAVES STATUS"-query must match server entries in the MaxSca configuration file. If the network configuration is such that this is not the case, the setting `assume_unique_hostnames` should be disabled. +## New Features + +* [MXS-1598](https://jira.mariadb.org/browse/MXS-1598) heartbeat replication don't support multimaster + ## Bug fixes +* [MXS-2189](https://jira.mariadb.org/browse/MXS-2189) optimistic_trx is rolled back if master fails +* [MXS-2187](https://jira.mariadb.org/browse/MXS-2187) Transaction replay is only attempted once +* [MXS-2186](https://jira.mariadb.org/browse/MXS-2186) SHOW DATABASES is routed to the master +* [MXS-2184](https://jira.mariadb.org/browse/MXS-2184) event_number is not incremented for updates +* [MXS-2179](https://jira.mariadb.org/browse/MXS-2179) Watchdog notifications must be generated also when users are fetched. +* [MXS-2178](https://jira.mariadb.org/browse/MXS-2178) Admin operations may cause systemd watchdog to be triggered. +* [MXS-2167](https://jira.mariadb.org/browse/MXS-2167) Monitors should be able to use extra_port +* [MXS-2158](https://jira.mariadb.org/browse/MXS-2158) Node rejoin fails, if the node was never a slave (but was master before going down) + ## Known Issues and Limitations There are some limitations and known issues within this version of MaxScale. From 8f0a85fd4670cc79342a18187f18f666a74b317a Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Wed, 28 Nov 2018 14:34:54 +0200 Subject: [PATCH 2/3] 2.3.2 is GA --- VERSION23.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION23.cmake b/VERSION23.cmake index bed6e9ed3..1f1cec23c 100644 --- a/VERSION23.cmake +++ b/VERSION23.cmake @@ -10,7 +10,7 @@ set(MAXSCALE_VERSION_PATCH "2" CACHE STRING "Patch version") # This should only be incremented if a package is rebuilt set(MAXSCALE_BUILD_NUMBER 1 CACHE STRING "Release number") -set(MAXSCALE_MATURITY "Beta" CACHE STRING "Release maturity") +set(MAXSCALE_MATURITY "GA" CACHE STRING "Release maturity") set(MAXSCALE_VERSION_NUMERIC "${MAXSCALE_VERSION_MAJOR}.${MAXSCALE_VERSION_MINOR}.${MAXSCALE_VERSION_PATCH}") set(MAXSCALE_VERSION "${MAXSCALE_VERSION_MAJOR}.${MAXSCALE_VERSION_MINOR}.${MAXSCALE_VERSION_PATCH}") From 0c973c1481dca1995739940026d6127a2ce9bf9d Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Wed, 28 Nov 2018 14:39:15 +0200 Subject: [PATCH 3/3] Update maintenance version --- VERSION23.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION23.cmake b/VERSION23.cmake index 1f1cec23c..43bfaaacf 100644 --- a/VERSION23.cmake +++ b/VERSION23.cmake @@ -5,7 +5,7 @@ set(MAXSCALE_VERSION_MAJOR "2" CACHE STRING "Major version") set(MAXSCALE_VERSION_MINOR "3" CACHE STRING "Minor version") -set(MAXSCALE_VERSION_PATCH "2" CACHE STRING "Patch version") +set(MAXSCALE_VERSION_PATCH "3" CACHE STRING "Patch version") # This should only be incremented if a package is rebuilt set(MAXSCALE_BUILD_NUMBER 1 CACHE STRING "Release number")