pathdb: Pathdb full write-buffer check #497
Merged
+10
−1
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
sebastianst
approved these changes
Feb 10, 2025
sebastianst
pushed a commit
that referenced
this pull request
Feb 26, 2025
* pathdb: limit diff layers in write-buffer * fork.yaml: document pathdb fix
sebastianst
pushed a commit
that referenced
this pull request
Feb 26, 2025
* pathdb: limit diff layers in write-buffer * fork.yaml: document pathdb fix
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.
Description
If we lose a large enough journal, then the state at startup of a full-node may be unavailable.
So prevent the write-buffer from growing too large, to keep the journal safe to delete.
Split into two commits, so the code-fix can be cherry-picked into upstream.
Metadata
(attempt to) Fix ethereum/go-ethereum#31131