influxdata / influxdata/influxdb

Potential Memory Leak: InfluxDB 2.5

Open
#23,950 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

kind/perf
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
We are seeing multiple users reporting large spikes in CPU and memory consumption since 2.5.
https://community.influxdata.com/t/cpu-utilization-of-influxdb-is-too-high/27458
https://influxcommunity.slack.com/archives/CH8RV8PK5/p1668601413474019
https://influxcommunity.slack.com/archives/CH8RV8PK5/p1667985792907689
https://community.influxdata.com/t/influxdb2-ram-consumption-inconsistent-over-longer-period/27465
https://github.com/influxdata/influxdb/issues/23930

__Expected behavior:__
InfluxDB should not be grabbing excessive amounts of CPU and memory on relatively low workloads.

__Actual behavior:__
InfluxDB performance should remain stable.

__Environment info:__

Seen on multiple deployments:

- AWS EC2 instance of type R5a.8xlarge.
- 60% CPU load on my 8 core ryzen 3700. Dashboard

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked community reports, Slack discussions, and issue #23930, then compare their deployment details with the AWS EC2 and Ryzen environments described here. A complete investigation would identify a reproducible cause and demonstrate stable CPU and memory use under relatively low workloads.

Written by the indexing model from the issue text.

Assessment

Domain
databases, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.