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

Document transaction_replay_max_size inner workings

Browse Source 
The documentation didn't explain how to estimate how much memory a
transaction takes and whether it was a global limit or a per session
limit.
This commit is contained in:
Markus Mäkelä 2020-06-01 16:22:14 +03:00
parent 2e1b0c5ddf
commit 11960a1e93
No known key found for this signature in database
GPG Key ID: 5CE746D557ACC499
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/Routers/ReadWriteSplit.md
View File

@ -446,8 +446,16 @@ be replayed successfully but it will still be attempted.
### `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)
that exceeds this limit will not be replayed. The default value is 1 MiB. This
limit applies at a session level which means that the total peak memory
consumption can be `transaction_replay_max_size` times the number of client
connections.
The amount of memory needed to store a particular transaction will be slightly
larger than the length in bytes of the SQL used in the transaction. If the limit
is ever exceeded, a message will be logged at the info level.
Read [the configuration guide](../Getting-Started/Configuration-Guide.md#sizes)
for more details on size type parameters in MaxScale.
### `optimistic_trx`