From 24ca503b0fd538285c456e8ba3bc621cfc00871f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Markus=20M=C3=A4kel=C3=A4?= Date: Fri, 17 May 2019 09:41:20 +0300 Subject: [PATCH] Document transaction_replay_attempts Also added the new readwritesplit parameters to the 2.4.0 release notes. --- .../MaxScale-2.4.0-Release-Notes.md | 18 ++++++++++++++++++ Documentation/Routers/ReadWriteSplit.md | 11 +++++++++++ 2 files changed, 29 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md index 119cb4411..33148302e 100644 --- a/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.4.0-Release-Notes.md @@ -156,6 +156,24 @@ For more information, read the [REST-API](../REST-API/Resources-Server.md#set-server-state) documentation for the `set` endpoint. +### Readwritesplit + +For more information on the readwritesplit router, refer to the +[documentation](../Routers/ReadWriteSplit.md). + +#### `transaction_replay_attempts` + +The new `transaction_replay_attempts` parameter controls how many errors the +transaction replay mechanism tolerates before giving up on the replay +attempt. The number of transaction replay attemps is now capped to a default +value of 5. + +#### `lazy_connect` + +Lazy connection creation delays the opening of all connections until they are +needed. This reduces the load that is placed on the backend servers when the +client connections are short. This feature is disabled by default. + ## Bug fixes [Here is a list of bugs fixed in MaxScale 2.4.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.4.0) diff --git a/Documentation/Routers/ReadWriteSplit.md b/Documentation/Routers/ReadWriteSplit.md index 0b2575087..3ce87aee6 100644 --- a/Documentation/Routers/ReadWriteSplit.md +++ b/Documentation/Routers/ReadWriteSplit.md @@ -489,6 +489,17 @@ that exceeds this limit will not be replayed. The default size limit is 1 MiB. Read [the configuration guide](../Getting-Started/Configuration-Guide.md#sizes) for more details on size type parameters in MaxScale. +### `transaction_replay_attempts` + +The upper limit on how many times a transaction replay is attempted before +giving up. The default value is 5. + +A transaction replay failure can happen if the server where the transaction is +being replayed fails while the replay is in progress. In practice this parameter +controls how many server and network failures a single transaction replay +tolerates. If a transaction is replayed successfully, the counter for failed +attempts is reset. + ### `optimistic_trx` Enable optimistic transaction execution. This parameter controls whether normal