influxdata / influxdata/kapacitor
kapacitor memory usage
Open
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Kapacitor 1.3.1 (git: master 3b5512f7276483326577907803167e4bb213c613)
500 alarm tasks
Currently, a single machine uses 96G memory, and the service is oom non-stop
Why does it take up so much memory?How should this problem be solved
This problem bothered me for half a year. It was too painful
Thank you very much
Contributor guide
Research direction
Start by reproducing the report with 500 alarm tasks on Kapacitor 1.3.1 and inspect the process's memory growth. Trace the relevant Go code to identify the cause of the out-of-memory behavior, then document a verified fix or mitigation and its effect on memory usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100