replication: do not ignore replica vclock on register
There was a bug in box_process_register. It decoded replica's vclock but never used it when sending the registration stream. So the replica might lose the data in range (replica_vclock, start_vclock). Follow-up #5566
Showing
- changelogs/unreleased/anon-register-gap.md 4 additions, 0 deletionschangelogs/unreleased/anon-register-gap.md
- src/box/box.cc 7 additions, 8 deletionssrc/box/box.cc
- test/replication/anon_register_gap.result 116 additions, 0 deletionstest/replication/anon_register_gap.result
- test/replication/anon_register_gap.test.lua 43 additions, 0 deletionstest/replication/anon_register_gap.test.lua
- test/replication/suite.cfg 1 addition, 0 deletionstest/replication/suite.cfg
- test/replication/suite.ini 1 addition, 1 deletiontest/replication/suite.ini
Loading
Please register or sign in to comment