[
https://issues.apache.org/jira/browse/SOLR-7344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14585255#comment-14585255
]
Yonik Seeley commented on SOLR-7344:
------------------------------------
{quote}
The current implementation is as follows,
- Whenever a request can not processed immediately, it is suspended and placed
on an internal queue.
- We associate a (configurable) timeout value with this request and attach a
callback (using Servlet 3 AsyncListener).
- Whenever the timeout occurs, we attempt to reschedule request. If a thread is
available for the corresponding request type, then the request goes through.
Otherwise we send the HTTP 503 error.
{quote}
Interesting, thanks for that.
After one request is finished, does something immediately try to pull another
request from the queue? Or do we need to wait for that timeout to hit?
> Allow Jetty thread pool limits while still avoiding distributed deadlock.
> -------------------------------------------------------------------------
>
> Key: SOLR-7344
> URL: https://issues.apache.org/jira/browse/SOLR-7344
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Mark Miller
> Attachments: SOLR-7344.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
