Continue if archival state is not in DB #5565
Merged
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.
This fixes #5555
When there's a finalized check point, a node enters in a migration phase to delete states that's not on the archival point. In previous iteration, a node will regenerate the state if the state does not exist on the migration point but that quickly becomes too buggy as the underlying block may not exist as well.
This PR went with the simpler approach to only preserve the state that is on the archival point.