From 31227e526b9a3cd969dda02eead01ecf92907a9d Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Mon, 23 Jan 2017 10:28:28 +0200 Subject: [PATCH] Add reference to "sizes" documentation --- Documentation/Routers/Binlogrouter.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/Documentation/Routers/Binlogrouter.md b/Documentation/Routers/Binlogrouter.md index 864f73c77..fe12fd470 100644 --- a/Documentation/Routers/Binlogrouter.md +++ b/Documentation/Routers/Binlogrouter.md @@ -140,10 +140,11 @@ a slave by MariaDB MaxScale when that slave is lagging behind the master. In this situation the slave is said to be in "catchup mode", this parameter is designed to both prevent flooding of that slave and also to prevent threads within MariaDB MaxScale spending disproportionate amounts of time with slaves -that are lagging behind the master. The burst size can be defined in Kb, Mb or -Gb by adding the qualifier K, M or G to the number given. The default value of -burstsize is 1Mb and will be used if burstsize is not given in the router -options. +that are lagging behind the master. The burst size can be provided as specified +[here](../Getting-Started/Configuration-Guide.md#sizes), except that IEC +binary prefixes can be used as suffixes only from MaxScale 2.1 onwards. +The default value is `1M`, which will be used if `burstsize` is not provided in +the router options. ### `mariadb10-compatibility`