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

MXS-2518 Document Clustrix and slave_selection_criteria

Browse Source
This commit is contained in:
Johan Wikman
2019-06-13 12:16:53 +03:00
parent 0b10b27ffd
commit f478386e47
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/Tutorials/MaxScale-Clustrix-Tutorial.md
View File

@ -150,6 +150,7 @@ user=maxscale
password=maxscale password=maxscale
cluster=Clustrix-Service cluster=Clustrix-Service
transaction_replay=true transaction_replay=true
slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS
``` ```
With this configuration, subject to the boundary conditions of With this configuration, subject to the boundary conditions of
transaction replaying, a client will neither notice group change 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 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).
**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, For detailed information about the transaction replay functionality,
please refer to the _readwritesplit_ please refer to the _readwritesplit_
[documentation](../Routers/ReadWriteSplit.md#transaction_replay). [documentation](../Routers/ReadWriteSplit.md#transaction_replay).