Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Erigon doesn't prune older logs any more #9889

Closed
somnathb1 opened this issue Apr 9, 2024 · 1 comment · Fixed by #9932
Closed

Erigon doesn't prune older logs any more #9889

somnathb1 opened this issue Apr 9, 2024 · 1 comment · Fixed by #9932
Assignees
Labels
bug Something isn't working imp1 High importance

Comments

@somnathb1
Copy link
Contributor

somnathb1 commented Apr 9, 2024

System information

Erigon version: ./erigon --version
2.59.0, 2.59.1, 2.59.2, 2.59.3

Chain/Network: All supported

Expected behaviour

Prune logs older than the provided value of the flag --prune.r.older

Actual behaviour

In subsequent sync after the initial sync, older logs are not deleted on a rolling basis. Although during initial sync the older logs are not stored. However, with time, this could lead to bloating of the database

Steps to reproduce the behaviour

Run the node with prune flags and check table sizes for TransactionLog table

@yperbasis yperbasis added imp2 Medium importance bug Something isn't working labels Apr 9, 2024
@somnathb1 somnathb1 self-assigned this Apr 9, 2024
@somnathb1 somnathb1 added imp1 High importance and removed imp2 Medium importance labels Apr 10, 2024
somnathb1 added a commit that referenced this issue Apr 15, 2024
@somnathb1
Copy link
Contributor Author

More improvements in #10019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working imp1 High importance
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants