raft: fix an assertion failure in raft_stop_candidate
There is a false assertion in raft_stop_candidate(): it assumes that the node must always have a running timer whenever it sees the leader. This is not true when the node is busy writing the new term on disk. Cover the mentioned case in the assertion. Closes #8169 NO_DOC=bugfix Co-authored-by:Sergey Ostanevich <sergos@tarantool.org> (cherry picked from commit df6cf5ec)
Showing
- changelogs/unreleased/gh-8169-raft-assert-on-wal-write.md 4 additions, 0 deletionschangelogs/unreleased/gh-8169-raft-assert-on-wal-write.md
- src/lib/raft/raft.c 4 additions, 2 deletionssrc/lib/raft/raft.c
- test/unit/raft.c 44 additions, 1 deletiontest/unit/raft.c
- test/unit/raft.result 7 additions, 1 deletiontest/unit/raft.result
Loading
Please register or sign in to comment