Introduce Optional Cap on Number Of Threads Per Query [LUCENE-8808]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
With the presence of #9802 , a natural progression is to allow advanced users to specify a cap on the number of threads a query can use. This is especially useful for long polled IndexSearcher instances, where the same instance is used to fire queries for multiple runs and there are multiple concurrent IndexSearcher instances on the same node.
This will be an optional parameter and local only to the IndexSearcher instance being configured during construction.
---
Migrated from [LUCENE-8808](https://issues.apache.org/jira/browse/LUCENE-8808) by Atri Sharma (@atris), updated May 24 2019
Contributor guide
Research direction
Start with IndexSearcher construction and the existing changes referenced by #9802. Trace how query execution chooses threads and define completion as an optional, instance-local cap that limits threads used by queries without affecting other IndexSearcher instances; no specific files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100