influxdata / influxdata/kapacitor
Kapacitor tasks interface (disable / enable / delete / define) slowness
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Kapacitor instance is having about 100 tasks and after running for about one week all task related queries becoming slow.
new task **define** or **disable** taking about **3 mins**,
it is running on Redhat , 64 GB ram, InfluxDB having about 12 databases and some 500 measurements.
if required, I can get trace output, tried to read myself but were not seeing anything other than **System Resource not available** for some of the threads, but nothing was mentioned about what resources it is looking for.
Otherwise system utilization looks all good.
Anyone having any clue ? any configuration changes or any unix level settings need to do ?
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
Start by reproducing the slow define, disable, enable, and delete operations with the reported task and database scale, then collect the trace output suggested in the issue. Investigate the reported “System Resource not available” messages; done means identifying the bottleneck and documenting or resolving the cause of the multi-minute operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100