You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Atri Sharma (Jira)" <ji...@apache.org> on 2019/12/02 10:39:00 UTC
[jira] [Commented] (LUCENE-9066) Modal Strategy In Concurrent Query
Execution
[ https://issues.apache.org/jira/browse/LUCENE-9066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16985954#comment-16985954 ]
Atri Sharma commented on LUCENE-9066:
-------------------------------------
[~jpountz] Agreed that we might not need the actual system statistics – queue length should be fine.
I opened LUCENE-9074 for adding queue length as a factor when allocating slices. I will open another Jira to check for the current queue length before creating a new thread for a given slice. This will ensure more dynamic behaviour for a system that is intermittently in and out of system stress.
> Modal Strategy In Concurrent Query Execution
> --------------------------------------------
>
> Key: LUCENE-9066
> URL: https://issues.apache.org/jira/browse/LUCENE-9066
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org