From f478386e47e6f6eff95464c937defd25d8fa92be Mon Sep 17 00:00:00 2001
From: Johan Wikman <johan.wikman@mariadb.com>
Date: Thu, 13 Jun 2019 12:16:53 +0300
Subject: [PATCH] MXS-2518 Document Clustrix and slave_selection_criteria

---
 Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md b/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md
index d1145317c..0373b1cd0 100644
--- a/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md
+++ b/Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md
@@ -150,6 +150,7 @@ user=maxscale
 password=maxscale
 cluster=Clustrix-Service
 transaction_replay=true
+slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS
 ```
 With this configuration, subject to the boundary conditions of
 transaction replaying, a client will neither notice group change
@@ -157,6 +158,11 @@ 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).
 
+**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).