From 9def07ab4ad485b4b47c3c2b03f2f288dd07bba5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Tue, 15 Jan 2019 18:24:14 +0200 Subject: [PATCH] Document connection_timeout behavior The fact that a warning is logged was not documented. --- Documentation/Getting-Started/Configuration-Guide.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Documentation/Getting-Started/Configuration-Guide.md b/Documentation/Getting-Started/Configuration-Guide.md index 1ecc81c90..1a689214e 100644 --- a/Documentation/Getting-Started/Configuration-Guide.md +++ b/Documentation/Getting-Started/Configuration-Guide.md @@ -1096,6 +1096,12 @@ default. To enable them, define the timeout in seconds in the service's configuration section. A value of zero is interpreted as no timeout, the same as if the parameter is not defined. +**Warning:** If a connection is idle for longer than the configured connection +timeout, it will be forcefully disconnected and a warning will be logged in the +MaxScale log file. If you are performing long-running maintenance operations +(e.g. `ALTER TABLE`) either do them with a direct connection to the server or +set `connection_timeout` to zero before executing them. + Example: ```