InfluxDB 3 At-Home Edition Crashes with OOM (Exit Code 137) After 3 Days Under Moderate Write Load

,
1

I’m running InfluxDB 3.0 At-Home Edition in Docker on a virtual machine with 32 GB of RAM.
There is a single database in InfluxDB 3 containing 4 tables (each with 4–8 tags). The write rate is approximately 1,000 lines per second. After about 3 days of operation, the system crashes with Docker exit code 137 (OOM exception).

I’ve reviewed the Performance Tuning recommendations on the official website and configured the following settings:

  • --exec-mem-pool-bytes=60%

  • --force-snapshot-mem-threshold=70%

However, this hasn’t resolved the issue.
How can I prevent this OOM error?

2

To avoid the OOM error, try to further lower InfluxDB’s memory use so it flushes data to disk sooner. Also try reducing --exec-mem-pool-bytes below 60% (for example 40%) and also lower --force-snapshot-mem-threshold (for example to 50%), so snapshots and Parquet writes happen earlier and data doesn’t build up in RAM. Try it and let us know.