From 1840937585148fb9bcad461a901badd4c26d7b66 Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Thu, 19 Nov 2015 18:28:29 +0200 Subject: [PATCH] Updated readwritesplit default values The combination of only one slave being used and the slave_selection_criteria being LEAST_CURRENT_OPERATIONS can possibly cause a connection pileup on one slave server. This would skew the query distribution heavily towards the first available slave even if multiple slave were being used. Having the maximum number of slave servers to be equal to the total amount of available slaves allows for a more even and responsive distribution of the query traffic. --- Routers/ReadWriteSplit.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Routers/ReadWriteSplit.md b/Routers/ReadWriteSplit.md index c6e5f456f..18a7aa3d4 100644 --- a/Routers/ReadWriteSplit.md +++ b/Routers/ReadWriteSplit.md @@ -52,7 +52,7 @@ passwd= ### `max_slave_connections` -**`max_slave_connections`** sets the maximum number of slaves a router session uses at any moment. Default value is `1`. +**`max_slave_connections`** sets the maximum number of slaves a router session uses at any moment. The default is to use all available slaves. max_slave_connections=