Hi all, So somewhat out of the blue today, the logs show this: ts=2025-07-01T16:27:05.591361Z lvl=info msg=“Error adding new TSM files from snapshot. Removing temp files.” log_id=0xMEzKc0000 service=storage-engine engine=tsm1 op_name=tsm1_cache_snapshot error=“cannot allocate memory” And then t…

@suyash , I appreciate the pointer. I’ve updated my cache settings from their default, and doubled them to this: “storage-cache-max-memory-size”: 2147483648, “storage-cache-snapshot-memory-size”: 52428800, 36 minutes and so far, so good. No “cannot allocate memory” errors. Thanks again, Dav…

So the crash happened again. So I increased the values by 4X. So they are now: storage-cache-snapshot-memory-size = 419430400 storage-cache-max-memory-size = 8589934592 We’ll see how long this lasts… Are there any recommended ways to calculate the desired values for these variables? It just…

Error="cannot allocate memory" leading to crash

suyash July 2, 2025, 8:55am 2

You probably want to review your memory settings for InfluxDB v2.x, see this similar question and answer for more information: Influx 2.6 using all memory of server total memory is 256 Gb

Topic		Replies	Views
Crash loop with "cannot allocate memory" influxdb	3	2262	November 11, 2020
Influxdb crash during start - Memory allocating issues InfluxDB 2 influxdb	2	1393	September 21, 2023
Cannot allocate memory when starting InfluxDB 2	5	690	April 21, 2023
Lvl=error msg="Failed to open shard"; "cannot allocate memory" InfluxDB 1 influxdb	1	229	August 6, 2024
Crash Allocate memoery InfluxDB 2 influxdb	5	1281	November 2, 2022

Error="cannot allocate memory" leading to crash

Related topics