From af91192498aaa7afe24eaf513959bf990089e662 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Wed, 3 Oct 2018 17:24:49 +0300 Subject: [PATCH] Add network throttling to release notes --- .../Release-Notes/MaxScale-2.3.0-Release-Notes.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md index 7ce42fa7c..432351608 100644 --- a/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.3.0-Release-Notes.md @@ -280,6 +280,16 @@ This allows conditional replication similar to _replicate_do_table_ but with full PCRE2 compliant match/exclude functionality. For more information, refer to the [binlogfilter](../Filters/BinlogFilter.md) documentation. +### Network Traffic Buffering + +The new +[`writeq_high_water`](../Getting-Started/Configuration-Guide.md#writeq_high_water) +and +[`writeq_low_water`](../Getting-Started/Configuration-Guide.md#writeq_low_water) +parameters allow network traffic to be throttled if it exceeds the highwater +mark. This can be used to prevent MaxScale from buffering too much data in +memory if the client is not reading results fast enough. + ## Bug fixes [Here is a list of bugs fixed in MaxScale 2.3.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.3.0)