I am using InfluxDB to store daily series for a bunch of fields. I notice that as I start populating data, the service will go down after a while. Further investigation shows that the wal directory is growing until several hundred MB and somehow causing high CPU usage and high disk read, followed by high memory usage, causing the whole service to refuse any further requests, and even the whole VM to go down.
Restarting the service doesn’t help, because it seems to process all files in the wal directory on start-up, and going down the same route as above.
The only solution so far is to stop the service and delete the wal directory before starting the service again. I know deleting the wal directory will lose some data so it is not a real solution…
I have left all configurations in influxdb.conf as default.
My VM spec is as follows:
CPU: 2 cores Azure vCPU
- Is InfluxDB not suitable for handling low frequency (daily) data?
- What do I do wrong that causes this issue?
- Any good solution?