Hello all, big problem here with v2.7.5 on Linux. The machine running influxd has plenty of resources (RAM, CPU, network). All runs OK for several (1+) hours and then, out of the blue, the query engine gets stuck. Queries are no longer run and new queries get queued until the queue gets full and then are not accepted any more. When this happens, influxd begins to use more CPU (but not much and not all the time) and its memory consumption begins to grow.
Writes still work OK, new data points are accepted and written OK. Our incoming fluxes are quite stable but there could be short bursts (couple of minutes maximum) from time to time.
At this point, either we restart influxd or we let it run and after some time (1 - 2 hours) the OOM killer kicks in.
Any hint?
P.S. I have collected metrics from several of these cases, if anyone is interested…