gh-837 "replica waits infinitely if the master has no xlogs"
This patch doesn't fix the bug itself, but simplifies matters so that there is no more .inprogress xlog files. .inprogress xlog files were created to start automatically from a state when the server crashed with an empty xlog, and couldn't create a new xlog since a file with the same LSN in the name already existed. To solve this problem, simply bump LSN at start if the last file in the recovery list had zero records in it. Emtpy xlog files still lead to panic if panic_on_wal_error=true during recovery.
Showing
- src/box/memtx_engine.cc 1 addition, 3 deletionssrc/box/memtx_engine.cc
- src/box/recovery.cc 13 additions, 58 deletionssrc/box/recovery.cc
- src/box/xlog.cc 23 additions, 93 deletionssrc/box/xlog.cc
- src/box/xlog.h 12 additions, 37 deletionssrc/box/xlog.h
- test/xlog/empty.result 1 addition, 1 deletiontest/xlog/empty.result
- test/xlog/empty.test.py 2 additions, 2 deletionstest/xlog/empty.test.py
- test/xlog/misc.result 8 additions, 9 deletionstest/xlog/misc.result
- test/xlog/misc.test.py 12 additions, 52 deletionstest/xlog/misc.test.py
Loading
Please register or sign in to comment