influxdata / influxdata/kapacitor

kapacitor high load memory

Open
#2,306 3 comments 0 reactions 0 assignees View on GitHub
question
Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Now, my kapacitor server is 30GB RAM (monitor about 200 host ). Mem-leak error lead to each 7 day it been restart. I'm try troubleshot log but found nothing.
I look at the guide kapacitor and found in frequently-asked-questions :

https://docs.influxdata.com/kapacitor/v1.5/troubleshooting/frequently-asked-questions/#how-does-kapacitor-handle-high-load

So it say: I must fix my stream script with add window node in it? Do i get it right? Can it resolve my problem ? I have ~200 tick-script, it's really painful to fix it.
And can you expand more detail about how windows work?
Thank you

Contributor guide

Open the contributing guide

Research direction

Start with the linked Kapacitor FAQ section on handling high load and review whether its explanation covers window nodes and stream scripts. Identify the missing detail requested by the issue, then document how windows relate to high-load behavior and whether the guidance applies to many TICKscripts. Done means the FAQ gives users clearer, actionable guidance.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.