feat: configurable pruning limits + span-rotation improves#134
Merged
pratikspatil024 merged 2 commits intoMar 27, 2026
Merged
Conversation
marcello33
approved these changes
Mar 11, 2026
pratikspatil024
approved these changes
Mar 12, 2026
manav2401
approved these changes
Mar 12, 2026
d24ab2a
into
0xPolygon:release/3.2-develop
9 checks passed
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
4 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.
This PR contains two improvements:
Added 4 environment variables to control pruning behavior:
ERIGON_PRUNE_LIMITandERIGON_PRUNE_TIMEOUT_MS: Control domain tables pruning (AccountsVals, StorageVals, CommitmentVals, CodeVals)ERIGON_PRUNE_CHANGESETS_LIMITandERIGON_PRUNE_CHANGESETS_TIMEOUT_MS: Control ChangeSets3 table pruningDefault limits (100-250ms for domains, 1000-500ms for ChangeSets) were insufficient for Polygon, causing CommitmentVals and ChangeSets3 tables to grow unbounded. This led to severe sync lags and excessive database size.
Increased limits to 10,000 entities with 2000ms timeouts, enabling effective pruning of accumulated data and maintaining MDBX database size within ~22GB.
Added on-chain timestamp gap validation to prevent false positives in span rotation detection.