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

Update release notes

Browse Source 
Added query classifier cache and moved ssl changes to the correct section.
This commit is contained in:
Markus Mäkelä
2018-08-22 09:08:10 +03:00
parent ad36a50e97
commit 518a4ef3bd
1 changed files with 15 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md
View File

@ -59,6 +59,11 @@ The `thread_stack_size` configuration parameter is ignored and has been
deprecated. If you need to explicitly set the stack size, do so using
`ulimit -s` before starting MaxScale.
### `ssl` for Servers and Listeners
The `ssl` parameter now accepts boolean values ìn addition to the old `required`
and `disabled` values.
## Dropped Features
### `log_to_shm` parameter and `--log=shm` option
@ -91,13 +96,18 @@ The CDC protocol no longer accepts the `QUERY-LAST-TRANSACTION` and
`QUERY-TRANSACTION` commands. They were removed due to the addition of the REST
API that provides the same information in a more easy to process format.
### `ssl` for Servers and Listeners
The `ssl` parameter now accepts boolean values ìn addition to the old `required`
and `disabled` values.
## New Features
### Query Classifier Cache
The query classifier now caches the results of each classification which
significantly improves performance of workloads that require query
classification. The default cache size limit is 40% of total system memory.
Read [the configuration guide](../Getting-Started/Configuration-Guide.md#query_classifier_cache_size)
for more information about the details of the query classifier cache and how to
configure it.
### Runtime Configuration of the Cache
With the variable `@maxscale.cache.enabled` it is now possible for a