From bd95ea2d357cfacdfdd782d78d1918a8da301e72 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 31 Dec 2015 15:45:32 +0200 Subject: [PATCH] MXS-451: Made documentation clearer about slave_selection_criteria The documentation for readwritesplit now clearly states that only connections from MaxScale are taken into consideration when slaves are being selected. --- Documentation/Routers/ReadWriteSplit.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Documentation/Routers/ReadWriteSplit.md b/Documentation/Routers/ReadWriteSplit.md index 11f9e7880..11ace959a 100644 --- a/Documentation/Routers/ReadWriteSplit.md +++ b/Documentation/Routers/ReadWriteSplit.md @@ -99,11 +99,13 @@ router_options=slave_selection_criteria= Where `` is one of the following values. -* `LEAST_GLOBAL_CONNECTIONS`, the slave with least connections in total -* `LEAST_ROUTER_CONNECTIONS`, the slave with least connections from this router +* `LEAST_GLOBAL_CONNECTIONS`, the slave with least connections from MaxScale +* `LEAST_ROUTER_CONNECTIONS`, the slave with least connections from this service * `LEAST_BEHIND_MASTER`, the slave with smallest replication lag * `LEAST_CURRENT_OPERATIONS` (default), the slave with least active operations +The `LEAST_GLOBAL_CONNECTIONS` and `LEAST_ROUTER_CONNECTIONS` use the connections from MaxScale to the server, not the amount of connections reported by the server itself. + ### `max_sescmd_history` **`max_sescmd_history`** sets a limit on how many session commands each session can execute before the session command history is disabled. The default is an unlimited number of session commands.