From 0c77514aaf65808edd94890d467af6b420313e04 Mon Sep 17 00:00:00 2001 From: Esa Korhonen Date: Mon, 26 Nov 2018 13:20:02 +0200 Subject: [PATCH] Update release notes Explains the default setting of assume_unique_hostnames. --- .../Release-Notes/MaxScale-2.3.2-Release-Notes.md | 9 +++++++++ 1 file changed, 9 insertions(+) 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 c7717ee27..6e0130955 100644 --- a/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md @@ -24,6 +24,15 @@ The default value of `connection_keepalive` is now 300 seconds. This prevents the connections from dying due to wait_timeout with longer sessions. This is especially helpful with pooled connections that stay alive for a very long time. +### MariaDBMonitor + +The monitor by default assumes that hostnames used by MaxScale to connect to the backends +are equal to the ones backends use to connect to each other. Specifically, for the slave +connections to be properly detected the `Master_Host` and `Master_Port` fields of the +output to "SHOW ALL SLAVES STATUS"-query must match server entries in the MaxScale +configuration file. If the network configuration is such that this is not the case, the +setting `assume_unique_hostnames` should be disabled. + ## Bug fixes ## Known Issues and Limitations