Reorganize Clustrix tutorial slightly
This commit is contained in:
@ -156,17 +156,16 @@ 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
|
||||||
events nor the disappearance of the very node the client is connected
|
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). For detailed
|
||||||
|
information about the transaction replay functionality, please refer
|
||||||
|
to the _readwritesplit_
|
||||||
|
[documentation](../Routers/ReadWriteSplit.md#transaction_replay).
|
||||||
|
|
||||||
**NOTE** It is vital to have
|
**NOTE** It is vital to have
|
||||||
`slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS`, as otherwise
|
`slave_selection_criteria=LEAST_GLOBAL_CONNECTIONS`, as otherwise
|
||||||
connections will **not** be distributed evenly across all Clustrix
|
connections will **not** be distributed evenly across all Clustrix
|
||||||
nodes.
|
nodes.
|
||||||
|
|
||||||
For detailed information about the transaction replay functionality,
|
|
||||||
please refer to the _readwritesplit_
|
|
||||||
[documentation](../Routers/ReadWriteSplit.md#transaction_replay).
|
|
||||||
|
|
||||||
As a rule of thumb, use _readwritesplit_ if it is important that
|
As a rule of thumb, use _readwritesplit_ if it is important that
|
||||||
changes taking place in the cluster configuration are hidden from the
|
changes taking place in the cluster configuration are hidden from the
|
||||||
applications, otherwise use _readconnroute_.
|
applications, otherwise use _readconnroute_.
|
||||||
|
Reference in New Issue
Block a user