From 4a2831e731e92d42c77ddf05138990f383823cd0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Wed, 9 Dec 2020 09:15:07 +0200 Subject: [PATCH] Clarify transaction_replay documentation The parameter controls three other parameters and overrides their configured values. --- Documentation/Routers/ReadWriteSplit.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Documentation/Routers/ReadWriteSplit.md b/Documentation/Routers/ReadWriteSplit.md index dea6e575b..1de36ba2d 100644 --- a/Documentation/Routers/ReadWriteSplit.md +++ b/Documentation/Routers/ReadWriteSplit.md @@ -428,8 +428,9 @@ The number of seconds to wait until an error is returned to the client when ### `transaction_replay` Replay interrupted transactions. This parameter was added in MaxScale 2.3.0 and -is disabled by default. Enabling this parameter implicitly enables both the -`delayed_retry` and `master_reconnection` parameters. +is disabled by default. Enabling this parameter enables both `delayed_retry` and +`master_reconnection` and sets `master_failure_mode` to `fail_on_write`, thereby +overriding any configured values for these parameters. When the server where the transaction is in progress fails, readwritesplit can migrate the transaction to a replacement server. This can completely hide the