influxdata / influxdata/kapacitor
Kapacitor fatal error: runtime: out of memory
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Kapacitor 1.3.0
Happens about once an hour. This is new. Same tick scripts for months.
I moved from a AWS t2.small to a t2.medium hoping moving from 2G to 4G would help.
What can I post as helpful diagnostics.
I generate about 100 events an hour.
I have 24 tick script.
About half are 60 second averaging, the other half 5 minutes.
Systems feeding into telegraf approx 100.
Is there a metric for memory requirements?
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.
Research direction
The report names Kapacitor 1.3.0, 24 tick scripts, approximately 100 events per hour, and about 100 Telegraf-fed systems, but no source files or tests. Start by collecting the helpful diagnostics requested in the issue and reproducing the hourly out-of-memory failure; done means identifying the cause or memory requirement and documenting a verified fix or workaround.
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
- 25/100