replication: persist confirmed vclock on replicas
Previously the replicas only persisted the confirmed lsn of the current synchronous transaction queue owner. As soon as the onwer changed, the info about which lsn was confirmed by the previous owner was lost. Actually, this info is needed to correctly filter synchro requests coming from the old term, so start tracking confirmed vclock instead of the confirmed lsn on replicas. In-scope of #9138 NO_TEST=covered by the next commit NO_CHANGELOG=internal change @TarantoolBot document Title: Document new IPROTO_RAFT_PROMOTE request field IPROTO_RAFT_PROMOTE and IPROTO_RAFT_DEMOTE requests receive a new key value pair: IPROTO_VCLOCK : MP_MAP The vclock holds a confirmed vclock of the node sending the request.
Showing
- src/box/applier.cc 5 additions, 2 deletionssrc/box/applier.cc
- src/box/box.cc 1 addition, 1 deletionsrc/box/box.cc
- src/box/memtx_engine.cc 6 additions, 2 deletionssrc/box/memtx_engine.cc
- src/box/relay.cc 3 additions, 2 deletionssrc/box/relay.cc
- src/box/txn_limbo.c 33 additions, 18 deletionssrc/box/txn_limbo.c
- src/box/txn_limbo.h 7 additions, 2 deletionssrc/box/txn_limbo.h
- src/box/xrow.c 25 additions, 4 deletionssrc/box/xrow.c
- src/box/xrow.h 9 additions, 2 deletionssrc/box/xrow.h
- test/unit/xrow.cc 3 additions, 2 deletionstest/unit/xrow.cc
Loading
Please register or sign in to comment