Stopping our event parsing logging from OOMing our read-only node #127
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
protolambda
added a commit
to protolambda/optimism
that referenced
this pull request
May 1, 2022
…engine-api ref impl: Engine API client bindings
bnoieh
pushed a commit
to bnoieh/optimism
that referenced
this pull request
Apr 3, 2024
…th_fermat fix(op-node): fix basefee when start new chain with fermat
bap2pecs
pushed a commit
to babylonlabs-io/optimism
that referenced
this pull request
Jul 31, 2024
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
We buffer interim debug log statements while converting EVM event logs to OVM event logs. Sometimes the volume of data logged (buffered) is large enough to cause our node to run out of memory. This makes it so we don't buffer nearly as much info.
Metadata
Fixes
Contributing Agreement