hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update max_slave_connections documentation

Browse Source 
Corrected the default value and added a more detailed explanation of what
the parameter does and how it affects client connections.
This commit is contained in:
Markus Mäkelä
2018-11-28 10:23:48 +02:00
parent 590e489be0
commit cb878f18b7
1 changed files with 21 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
Documentation/Routers/ReadWriteSplit.md
View File

@ -34,9 +34,28 @@ For more details about the standard service parameters, refer to the
### `max_slave_connections`
**`max_slave_connections`** sets the maximum number of slaves a router session
uses at any moment. The default is to use all available slaves.
uses at any moment. The default is to use at most 255 slave connections per
client connection. In older versions the default was to use all available slaves
with no limit.
max_slave_connections=<max. number, or % of available slaves>
```
max_slave_connections=<max. number, or % of available slaves>
```
For example, if you have configured MaxScale with one master and three slaves
and set `max_slave_connections=2`, for each client connection a connection to
the master and two slave connections would be opened. The read query load
balancing is then done between these two slaves and writes are sent to the
master.
By tuning this parameter, you can control how dynamic the load balancing is at
the cost of extra created connections. With a lower value of
`max_slave_connections`, less connections per session are created and the set of
possible slave servers is smaller. With a higher value in
`max_slave_connections`, more connections are created which requires more
resources but load balancing will almost always give the best single query
response time and performance. Longer sessions are less affected by a high
`max_slave_connections` as the relative cost of opening a connection is lower.
### `max_slave_replication_lag`