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

Update release notes

Browse Source 
Explains the default setting of assume_unique_hostnames.
This commit is contained in:
Esa Korhonen 2018-11-26 13:20:02 +02:00
parent 19ad915685
commit 0c77514aaf
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Documentation/Release-Notes/MaxScale-2.3.2-Release-Notes.md
View File

@ -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