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

Lodestar got OOM during big unfinality period #7240

Closed
twoeths opened this issue Nov 26, 2024 · 0 comments · Fixed by #7241
Closed

Lodestar got OOM during big unfinality period #7240

twoeths opened this issue Nov 26, 2024 · 0 comments · Fixed by #7241
Assignees
@twoeths
Labels
meta-bug Issues that identify a bug and require a fix.

Comments

@twoeths
Copy link
Contributor

twoeths commented Nov 26, 2024

Describe the bug

Lodestar prunes checkpoint state cache during synced, but when network is at unfinality period and we restart the node, there are too many states in memory, we did not prune it and it caused OOM

Image

Node is restarted multiple times

Image

Expected behavior

we should prune checkpoint states during sync time when we restart the node

Steps to reproduce

No response

Additional context

No response

Operating system

Linux

Lodestar version or commit hash

v1.23.0
@twoeths twoeths added the meta-bug Issues that identify a bug and require a fix. label Nov 26, 2024
@twoeths twoeths self-assigned this Nov 26, 2024
@twoeths twoeths mentioned this issue Nov 26, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@twoeths twoeths

Labels
meta-bug Issues that identify a bug and require a fix.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: prune checkpoint states at syncing time ChainSafe/lodestar
1 participant
@twoeths