replication: rebootstrap instance on startup if it fell behind
If a replica fell too much behind its peers in the cluster and xlog files needed for it to get up to speed have been removed, it won't be able to proceed without rebootstrap. This patch makes the recovery procedure detect such cases and initiate rebootstrap procedure if necessary. Note, rebootstrap is currently only supported by memtx engine. If there are vinyl spaces on the replica, rebootstrap will fail. This is fixed by the following patches. Part of #461
Showing
- src/box/box.cc 9 additions, 0 deletionssrc/box/box.cc
- src/box/replication.cc 59 additions, 0 deletionssrc/box/replication.cc
- src/box/replication.h 9 additions, 0 deletionssrc/box/replication.h
- test/replication/replica_rejoin.result 247 additions, 0 deletionstest/replication/replica_rejoin.result
- test/replication/replica_rejoin.test.lua 92 additions, 0 deletionstest/replication/replica_rejoin.test.lua
- test/replication/suite.cfg 1 addition, 0 deletionstest/replication/suite.cfg
test/replication/replica_rejoin.result
0 → 100644
test/replication/replica_rejoin.test.lua
0 → 100644
Please register or sign in to comment