Description
Currently TX SQL protocol works as follows:
1) Lock request is sent to PRIMARY node where updates are applied immediately.
2) Updated values are stored in-memory
3) When commit command is issued, updates are propagated to {{BACKUP}}s.
This requires data to be stored in memory at some point. We should design better protocol which will allow for updates to be propagated to backups efficiently.
Ticket is related (or may be even duplicates) to IGNITE-7186.
Attachments
Issue Links
- Is contained by
-
IGNITE-4191 SQL: support transactions
-
- Resolved
-
- relates to
-
IGNITE-8371 MVCC TX: Force key request during rebalance may cause error on backups.
-
- Resolved
-