From 00e21497603a534b645b8a6c2b181d08c487071c Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Tue, 13 Dec 2016 09:22:51 +0200 Subject: [PATCH] Add mention `retry_failed_reads` in release notes The release notes now mention the new `retry_failed_reads` option for readwritesplit. --- .../Release-Notes/MaxScale-2.1.0-Release-Notes.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md b/Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md index c539b49d7..8cfc18482 100644 --- a/Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md +++ b/Documentation/Release-Notes/MaxScale-2.1.0-Release-Notes.md @@ -57,6 +57,15 @@ by default, is configured using the new global configuration entry `log_throttli For more information about this configuration entry, please see [Global Settings](../Getting-Started/Configuration-Guide.md#global-settings). +### Readwritesplit Read Retry + +In 2.1, Readwritesplit will retry failed SELECT statements that are +executed outside of transaction and with autocommit enabled. This allows +seamless slave failover and makes it transparent to the client. + +Read the [Readwritesplit documentation](../Routers/ReadWriteSplit.md) on +`retry_failed_reads` for more details. + ### Persistent Connections Starting with the 2.1 version of MariaDB MaxScale, when a MySQL protocol