Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.0 -> main] Fix unlinkable block exceptions when block-log-retain-blocks = 0 #2009

Merged
merged 3 commits into from
Dec 20, 2023

Conversation

heifner
Copy link
Member

@heifner heifner commented Dec 20, 2023

When running with block-log-retain-blocks = 0, many unlinkable block exceptions were generated.

Do not attempt to apply blocks that are before LIB.

Blocks are received before LIB because we always sync from LIB to make sure we see all possible forks. However, between the request and the blocks coming in, LIB can move. When running with no block log, these blocks are not known to have already been processed. However, there is never any reason to attempt to apply blocks that are <= LIB, so just drop them instead of attempting to apply them.

Merges release/5.0 into main including #2007

Resolves #2006

@heifner heifner added the OCI Work exclusive to OCI team label Dec 20, 2023
@heifner heifner merged commit 952aedf into main Dec 20, 2023
26 checks passed
@heifner heifner deleted the GH-2006-unlinkable-blocks-main branch December 20, 2023 16:48
@ericpassmore
Copy link
Contributor

Note:start
group: STABILITY
category: BUG
summary: Account for LIB movement between request and receiving blocks by dropping blocks before LIB.
Note:end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
OCI Work exclusive to OCI team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When setting block-log-retain-blocks = 0 get lots of unlinkable blocks errors
4 participants