influxdata / influxdata/influxdb
Memory usage doubled after deleting nothing at all
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Hi,
Using 1.7.9 on CentOS 7.7, RPM's provided by InfluxData.
I have a very large database (983GB), holding nearly 1 year worth of data, across multiple measurements. I'd say a quarter of that is in the "interrupts" measurement. Today I issued a query such as: delete from "interrupts" where time < '2019-01-01'. I have no points matching that, the oldest shard is from 2019-02-01.
Usually, influxd process uses ~30% of RAM (that's roughly 75GB of total 256GB). The query took a long time. I didn't time it, but it was around 45 mins. During it, RAM usage slowly climbed up. After it finished, influxd process now uses 65% of RAM, and doesn't seem to want to let go.
I attach the usual debug files.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.