txn_limbo: filter rows based on known peer terms
Start writing the actual leader term together with the PROMOTE request
and process terms in PROMOTE requests on receiver side.
Make applier only apply synchronous transactions from the instance which
has the greatest term as received in PROMOTE requests.
Closes #5445
Co-developed-by:
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Showing
- changelogs/unreleased/qsync-multi-statement-recovery.md 0 additions, 0 deletionschangelogs/unreleased/qsync-multi-statement-recovery.md
- changelogs/unreleased/raft-promote.md 4 additions, 0 deletionschangelogs/unreleased/raft-promote.md
- src/box/applier.cc 57 additions, 1 deletionsrc/box/applier.cc
- src/box/box.cc 12 additions, 6 deletionssrc/box/box.cc
- src/box/txn_limbo.c 29 additions, 5 deletionssrc/box/txn_limbo.c
- src/box/txn_limbo.h 40 additions, 0 deletionssrc/box/txn_limbo.h
- test/replication/gh-5445-leader-inconsistency.result 292 additions, 0 deletionstest/replication/gh-5445-leader-inconsistency.result
- test/replication/gh-5445-leader-inconsistency.test.lua 129 additions, 0 deletionstest/replication/gh-5445-leader-inconsistency.test.lua
- test/replication/suite.cfg 1 addition, 0 deletionstest/replication/suite.cfg
Loading
Please register or sign in to comment