You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
🙂 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
Let it running for some time and take note of memory consumption always increasing.
You could shell into the
node
container and look for thecartesi-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.
The text was updated successfully, but these errors were encountered: