From 1df6495d9ab7f9bdc3fbe351fe2708ee04bb846a Mon Sep 17 00:00:00 2001 From: Esa Korhonen Date: Wed, 8 May 2019 15:29:00 +0300 Subject: [PATCH] Update release notes on MariaDB-Monitor change --- .../Release-Notes/MaxScale-2.2.21-Release-Notes.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md index d2f54c46d..7d0c2228d 100644 --- a/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.2.21-Release-Notes.md @@ -13,6 +13,13 @@ report on [our Jira](https://jira.mariadb.org/projects/MXS). * [MXS-2410](https://jira.mariadb.org/browse/MXS-2410) Hangup delivered to wrong DCB * [MXS-2366](https://jira.mariadb.org/browse/MXS-2366) Wrong tarball RPATH +## Changes to MariaDB-Monitor failover + +Failover is no longer disabled permanently if it or any other cluster operation fails. +The disabling is now only temporary and lasts for 'failcount' monitor iterations. Check +[MariaDB-Monitor documentation](../Monitors/MariaDB-Monitor.md#limitations-and-requirements) +for more information. + ## Known Issues and Limitations There are some limitations and known issues within this version of MaxScale.