Yeah the problem is that the raft framework we use does not give a good indication of where the leader's log is, so the scenario you explained could occur, if there have been a large number of writes in the backlog. We will have to explicitly query the leader to fetch that information as part of the reindexing process at startup. This is in our radar, but we haven't gotten around to it yet.