From 4276514e275c1d12ce7c9721c059dd3cbc535c4b Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Thu, 28 Mar 2019 14:06:25 +0200 Subject: [PATCH] MXS-2363 Add section to release notes Also fix some minor other things in the relase notes. --- .../MaxScale-2.4.0-Release-Notes.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md index 65b1fa0b3..825ac9f20 100644 --- a/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md @@ -76,6 +76,8 @@ being drained is the master, then it will not be possible to connect unless `master_failure_mode` has been set to something else but the default `fail_instantly`. +Once the server has been drained, the state will be `Drained`. + ### Cluster The servers a service uses can now be specified using the `cluster` @@ -101,6 +103,21 @@ for details. _Not_ providing an explicit unit has been deprecated in MaxScale 2.4. +### Query Classifier Cache + +It is now possible to examine the contents of the query classifier cache. +The REST-API endpoint is +``` +/v1/maxscale/query_classifier/cache +``` +and the equivalent _maxctrl_ command +``` +maxctrl show qc_cache +``` +The output shows the statements (the canonical version) in the cache, +the number of times they have been encountered and how they have been +classified. + ## Bug fixes [Here is a list of bugs fixed in MaxScale 2.4.0.](https://jira.mariadb.org/issues/?jql=project%20%3D%20MXS%20AND%20issuetype%20%3D%20Bug%20AND%20status%20%3D%20Closed%20AND%20fixVersion%20%3D%202.4.0)