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.

Sign up for GitHub

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

Jump to bottom

Graceful handling of MapFull error in slasher #1890

Closed
michaelsproul opened this issue Nov 12, 2020 · 2 comments
Closed

Graceful handling of MapFull error in slasher #1890

michaelsproul opened this issue Nov 12, 2020 · 2 comments
Assignees
@michaelsproul
Labels
A0

Comments

@michaelsproul
Copy link
Member

Description

The slasher (#1567) is capable of setting a max-db-size for LMDB, but it's currently quite useless in that once the max size is reached, the slasher never recovers from the MapFull errors that get returned. I made a tweak that I thought would allow pruning to run (and clear some space), but pruning itself fails with a MapFull error, even though it only does gets and deletes 🤔
@michaelsproul michaelsproul self-assigned this Nov 12, 2020
This was referenced Nov 22, 2020
Closed
Closed
@bors bors bot closed this as completed in 7d64410 Nov 23, 2020
@michaelsproul
Copy link
Member Author

I think this is still an issue, based on the fact that slasher DB sizes are steadily increasing.

@michaelsproul michaelsproul reopened this Mar 26, 2021
This was referenced Mar 26, 2021
Closed
Closed
@michaelsproul
Copy link
Member Author

Closing in favour of #2286, as I think our disk usage issues are not due to a bug in pruning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelsproul michaelsproul

Labels
A0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Merged by Bors] - Tweak slasher DB schema and pruning sigp/lighthouse
1 participant
@michaelsproul