leader: do not perform blockstore check in next_leader_slot #2445
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
next_leader_slot
will skip over any group of 4 leader slots if there is a shred present for the first leader slot. This can lead to accidentally skipping leader slots where only the first block has been produced in cases of reset to an earlier slot.Summary of Changes
Instead remove the blockstore check entirely. In
poh_recorder
, if we've ticked past our last slot, recompute the next leader slot's tick heights to be used instead. This builds on #2416 which performs the blockstore check inpoh_recorder