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
In the last 24hrs my PR has repeatedly been killed by OS for 'Out of Memory' requiring restarting, it is running unmodified 26.1 and uses RocksDB.
Turning voting off didn't change the outcome, issue wasn't present in earlier periods of high traffic. Haven't seen similar issues on other nodes running lmdb backends.
Example Restarts:
Start time: Sun Mar 3 05:17:49 2024 UTC
Start time: Sun Mar 3 05:37:15 2024 UTC
Start time: Sun Mar 3 06:02:41 2024 UTC
Start time: Sun Mar 3 06:42:35 2024 UTC
Start time: Sun Mar 3 07:33:08 2024 UTC
Outcome: Following more analysis it appeared that the RPC 'representatives_online' was consuming large amounts of ram due to the recent spamming of representatives which was causing the node to crash - to fix this the RPC command was aggressively cached.
This is now being fixed in PR #4482
Summary
In the last 24hrs my PR has repeatedly been killed by OS for 'Out of Memory' requiring restarting, it is running unmodified 26.1 and uses RocksDB.
Turning voting off didn't change the outcome, issue wasn't present in earlier periods of high traffic. Haven't seen similar issues on other nodes running lmdb backends.
Example Restarts:
dmesg output:
Running
perf
Node version
26.1
Build details
Network: live, version: V26.1
Build Info: 66d74ff "GNU C++ version " "12.2.0" "BOOST 108100" BUILT "Feb 28 2024"
Database backend: RocksDB 7.8.3
4 core, 8Gb Ram, 5G Swap
OS and version
Ubuntu 23.04 (GNU/Linux 6.2.0-20-generic x86_64)
Steps to reproduce the behavior
Expected behavior
Node has run for many months without these issues.
Actual behavior
Repeatedly being killed due to out of memory (nano-node is clearly using the largest amount) - could this be due to the RocksDB itself?
Possible solution
No response
Supporting files
No response
The text was updated successfully, but these errors were encountered: