From f5c239cc8d398ecdff62e45eaa6ee17a20d4a6a7 Mon Sep 17 00:00:00 2001 From: Johan Wikman Date: Thu, 13 Jun 2019 14:52:13 +0300 Subject: [PATCH] Reorganize Clustrix tutorial slightly --- Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md b/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md index 0373b1cd0..ddce84450 100644 --- a/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md +++ b/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md @@ -156,17 +156,16 @@ With this configuration, subject to the boundary conditions of transaction replaying, a client will neither notice group change events nor the disappearance of the very node the client is connected to. In that latter case, MaxScale will simply connect to another node -and replay the current transaction (if one is active). +and replay the current transaction (if one is active). For detailed +information about the transaction replay functionality, please refer +to the _readwritesplit_ +[documentation](../Routers/ReadWriteSplit.md#transaction_replay). **NOTE** It is vital to have `slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS`, as otherwise connections will **not** be distributed evenly across all Clustrix nodes. -For detailed information about the transaction replay functionality, -please refer to the _readwritesplit_ -[documentation](../Routers/ReadWriteSplit.md#transaction_replay). - As a rule of thumb, use _readwritesplit_ if it is important that changes taking place in the cluster configuration are hidden from the applications, otherwise use _readconnroute_.