feat(disk): handle disk maxing out better#555
Open
OisinKyne wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
1 participant
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.
Summary
My node is crashing because its maxing out on disk because reth default is archive and takes up > 85% of a 4TB disk, and thus gets pods evicted for disk pressure.
This changes the default to full node, makes archive an option (idt i've tested this beyond reth)
Also fixes a linux bug for showing disk free, to warn about this earlier.
Good future scope would be allowing to sync a more selective archive node, e.g. only after a certain block, if you're trying to index a modern DeFi app/use case.