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

MXS-1507: Clarify transaction replay limitations

Browse Source 
Only transactions that return identical results can be replayed.
This commit is contained in:
Markus Mäkelä 2018-04-23 11:43:28 +03:00
parent 7de7e7b2fe
commit cb5917b346
No known key found for this signature in database
GPG Key ID: 72D48FCE664F7B19
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/Routers/ReadWriteSplit.md
View File

@ -351,8 +351,9 @@ are met, the transaction can be safely replayed.
* The replacement server where the transaction is applied returns results
identical to the original partial transaction.
If the results from the replacement server are not identical when the
transaction is replayed, the client connection is closed.
If the results from the replacement server are not identical when the transaction is
replayed, the client connection is closed. This means that any transaction with a server
specific result (e.g. `NOW()`, `@@server_id`) cannot be replayed.
Performing MVCC reads (`SELECT` queries without `FOR UPDATE` or `LOCK IN SHARE MODE`)
with transaction replay is discouraged. If such statements are executed