chore: set event logs from StaticFileProducer and Pruner to debug
#13080
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
joshieDo
added
the
A-observability
joshieDo
requested review from
mattsse,
Rjected,
onbjerg,
emhane and
klkvr
as code owners
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.
related to #7732 (comment)
Pruner does run in archival node because right now, we write to both database and static files when saving blocks during live sync (issue: #11918). Until that is handled, we need to have the pruner running as to clean-up the duplicated data.
What we can do is downgrades the event logs from
StaticFileProducerandPrunertodebug, as not to potentially confuse users when running archival nodes.