quickwit-oss / quickwit-oss/quickwit
Improving placement
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Given one index, we attempt to spread the load on as few indexer as possible to have better split pruning.
The current logic has some pitfalls:
- Assuming the algorithm ends up spreading the load over two indexers, it does not attempt to do that evenly at all.
- If we have one indexer up, and it receives N pipelines, and more indexers are added. If the N pipeline do not
exceed the cpu capacity of the one indexer, the new indexers won't get any of the load.
These are not critical (we are always below the load we target), but they seem to be confusing users.
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
No file, test, or entry point is named; begin by locating the indexer placement and pipeline load-balancing logic, then inspect any existing tests around it. Done means placement is more even when using two indexers and newly added indexers can receive load when the original indexer remains below target capacity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100