influxdata / influxdata/kapacitor
Is there a limit on the number of scripts Kapacitor can handle?
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
Hi all,
I've found an answer to this question in FAQs:
> There is no software limit, but it will be limited by available server resources.
But I'm thinking in 60k-120k scripts (maybe 300k), so I'm not sure if this numbers are insane or, maybe, Kapacitor can do it.
My problem is this:
I have different measurements (60k) all of them with the same schema: Four fields (f1, f2, f3, & f4) and one tag. Fields f1, f2, and f3 are always strings, but f4 can be floats, integers, or strings depending on the measurement.
I'm using this query in Kapacitor (in a batch task) to take the data from InfluxDB: `SELECT f1, f2, f3, f4 FROM "db_name"."rp_name"./.*/ WHERE ...` but when f4 is a string it doesn't return values. This issue is related to InfluxDB, not Kapacitor. More info:
1. https://github.com/influxdata/influxdb/issues/10022
2. https://github.com/influxdata/influxdb/issues/10042
Using a stream task is not an option to me, so I've thought about creating a script per measurement (60k). Is this possible?? Can Kapacitor handle it?
Btw, rigth now, I have 5 TICKscripts, so this is why ' thinking in 300k=5*60k TICKscripts
Contributor guide
Research direction
Start with the FAQ statement and the linked InfluxDB issues #10022 and #10042 to understand the reported query limitation. Then investigate whether Kapacitor's batch-task model supports the proposed per-measurement scale; done means a confirmed capacity answer or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100