chore(l1, l2): remove rocksdb wal TTL #4966
Merged
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
Lines of code reportTotal lines added: Detailed view |
MegaRedHand
approved these changes
Oct 22, 2025
ilitteri
approved these changes
Oct 22, 2025
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 22, 2025
**Motivation** We currently have a 1 hour ttl for our rocksdb WAL for no discernible reason, and I think it's better to leave it to rocksdb to configure until we find a reason to change it. This 1 hour ttl is the main reason why the database size for our nodes drops massively an hour after snap sync finishes (in mainnet this drop is of more than 100 GB) **Description** <!-- A clear and concise general description of the changes this PR introduces --> <!-- Link to issues: Resolves #111, Resolves #222 --> Closes #issue_number
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation
We currently have a 1 hour ttl for our rocksdb WAL for no discernible reason, and I think it's better to leave it to rocksdb to configure until we find a reason to change it.
This 1 hour ttl is the main reason why the database size for our nodes drops massively an hour after snap sync finishes (in mainnet this drop is of more than 100 GB)
Description
Closes #issue_number