quickwit-oss / quickwit-oss/quickwit
search nodes unresponsive with expensive aggregation
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
As reported:
If I do an aggregation over a large time span, the searchers will end up being killed by kubernetes for missing health checks. I'd assume because the CPU usage is too high and they are mostly un-responsive
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 an aggregation over a large time span and observe the searchers' Kubernetes health checks and CPU usage. Trace the searcher path responsible for the unresponsive health checks; done means expensive aggregations no longer cause searchers to be killed for missing health checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, performance, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100