txn_limbo: don't duplicate confirmations in WAL
When an ACK was received for an already confirmed transaction whose CONFIRM WAL write is in progress, it produced a second CONFIRM in WAL with the same LSN. That was unnecessary work taking time and disk space for WAL records. Although it didn't lead to any bugs. Just was very inefficient. This patch makes confirmation LSN monotonically grow. In case more ACKs are received for an already confirmed LSN, its confirmation is not written second time. Closes #5144
Showing
- src/box/txn_limbo.c 7 additions, 2 deletionssrc/box/txn_limbo.c
- src/box/txn_limbo.h 8 additions, 0 deletionssrc/box/txn_limbo.h
- test/replication/gh-5144-qsync-dup-confirm.result 153 additions, 0 deletionstest/replication/gh-5144-qsync-dup-confirm.result
- test/replication/gh-5144-qsync-dup-confirm.test.lua 72 additions, 0 deletionstest/replication/gh-5144-qsync-dup-confirm.test.lua
- test/replication/replica1.lua 1 addition, 0 deletionstest/replication/replica1.lua
- test/replication/replica2.lua 1 addition, 0 deletionstest/replication/replica2.lua
- test/replication/suite.ini 1 addition, 1 deletiontest/replication/suite.ini
test/replication/replica1.lua
0 → 120000
test/replication/replica2.lua
0 → 120000
Please register or sign in to comment