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

MXS-1507: Add transaction size limit

Browse Source 
Added the `transaction_replay_max_size` parameter that controls the
maximum size of a transaction that can be replayed. If the limit is
exceeded, the stored statements are released thus preventing the
transaction from being replayed.

This limitation prevents accidental misuse of the transaction replaying
system when autocommit is disabled. It also allows the user to control the
amount of memory that MaxScale will use.
This commit is contained in:
Markus Mäkelä
2018-04-25 10:50:43 +03:00
parent cffed86962
commit 092532745d
6 changed files with 53 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Documentation/Routers/ReadWriteSplit.md
View File

@ -360,6 +360,13 @@ with transaction replay is discouraged. If such statements are executed
but the results of each reply are identical, the transaction is replayed but the results
are not guaranteed to be consistent on the database level.
### `transaction_replay_max_size`
The limit on transaction size for transaction replay in bytes. Any transaction
that exceeds this limit will not be replayed. The default size limit is 1
MiB. Read [the configuration guide](../Getting-Started/Configuration-Guide.md#sizes)
for more details on size type parameters in MaxScale.
## Routing hints
The readwritesplit router supports routing hints. For a detailed guide on hint