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

Memory Leak or Excessive RocksDB Memory Usage #2959

Open
2anoubis opened this issue Feb 12, 2025 · 0 comments
Open

Memory Leak or Excessive RocksDB Memory Usage #2959

2anoubis opened this issue Feb 12, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@2anoubis
Copy link

Bug Report

Bug: RocksDB Memory Consumption Unbounded, Leading to Excessive RAM Usage

Description

The Taraxa node, with built in with RocksDB, does not appear to have memory consumption limits. This results in RocksDB potentially consuming all available system memory, growing to over 70GB in some observed cases. This behavior makes the node unstable and can lead to server crashes. We need to expose RocksDB configuration parameters related to memory management to allow operators to control memory usage.

Steps to Reproduce

  1. Run a mainnet registered Taraxa node (v1.12.7) on a server with 64-128GB of RAM.
  2. Allow the node to run for approximately two days.

Expected Result

The node should consume a reasonable and stable amount of RAM, leaving sufficient memory for other system processes. The memory usage should be configurable and predictable.

Actual Results

The node consumes all available RAM, in some cases exceeding 70GB. This excessive memory usage leads to performance degradation and potential server instability.

Environment

Node version

v1.12.7

Operating System details.

docker container

@2anoubis 2anoubis added the bug Something isn't working label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant