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

state-server high memory usage #513

Open
endersonmaia opened this issue Jul 10, 2024 · 0 comments
Open

state-server high memory usage #513

endersonmaia opened this issue Jul 10, 2024 · 0 comments
Labels
! High priority
Milestone

Comments

@endersonmaia
Copy link
Contributor

🙂 Expected behavior

The memory consumption of the node should not increase over time indefinitely.

🫠 Actual behavior

A rollups-node running for some time will eventually be killed by OOM since the state-server is always consuming more memory and never releasing it.

🧪 Minimal test case

make docker-run
#on another terminal 
docker stats

Let it running for some time and take note of memory consumption always increasing.

You could shell into the node container and look for the cartesi-rollups-state-server process memory usage individually.

🌎 Environment

This was observed with 1.5.0, but can happen with previous versions also, since the state-server component isn't updated for some rollups-node releases back.

✔️ Possible solutions

Make state-server persist data to disk or release memory that is not needed anymore.

@endersonmaia endersonmaia added the bug Something isn't working label Jul 10, 2024
@marcelstanley marcelstanley self-assigned this Jul 10, 2024
@marcelstanley marcelstanley moved this to 📋 Backlog in Node Unit Jul 10, 2024
@marcelstanley marcelstanley added the ! High priority label Jul 10, 2024
@marcelstanley marcelstanley changed the title state-server memory leak state-server high memory usage Jul 19, 2024
@marcelstanley marcelstanley added this to the TBD milestone Jul 26, 2024
@marcelstanley marcelstanley removed their assignment Aug 7, 2024
@marcelstanley marcelstanley modified the milestones: TBD, 1.6 Aug 7, 2024
@marcelstanley marcelstanley removed the bug Something isn't working label Aug 8, 2024
@marcelstanley marcelstanley removed the status in Node Unit Aug 9, 2024
@marcelstanley marcelstanley moved this to 📋 Backlog in Node Unit Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
! High priority
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants