Replayer, next slot not orphaned #13765
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When replaying from a checkpoint file, the start slot may not be occupied by a slot. In that case, find the next slot occupied by the slot.
The replayer was choosing that next slot to replay from, regardless of its chain status. Make sure the status is not
orphaned, otherwise we won't find the block in the chain chosen by the replayer.The berkeley replayer cron job failed because it tried to replay from an orphaned slot. The fix was made for the berkeley replayer in #13715.
Update the
devnetandmainnetcron jobs to use an image from this PR.