Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
New
Description
When executing a query concurrently today, we do not take any sort of system statistics into account. For e.g. if the node is under high pressure, it is not advisable to spawn a large number of threads for a query since they are most likely to be blocked waiting for CPU to be available. However, the converse is that for a lightly loaded cluster, the query can consume as many threads as required.
This Jira tracks high level efforts in this direction. The first idea is to account the Executor's wait queue's size as a factor when allocating slices to a query's segments.
Attachments
Issue Links
- is a parent of
-
LUCENE-9075 Check Current System Pressure Before Allocating a New Thread In Concurrent Search
- Open
-
LUCENE-9074 Account for Executor's Queue Length When Planning Slices in IndexSearcher
- Closed