[
https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193750#comment-13193750
]
Mikhail Khludnev commented on SOLR-1093:
----------------------------------------
1. is there a way to dispatch separate queries by the webcontainer threads?
2. otherwise it requires separate thread pool. It makes operations support more
complicated and less predictable. I suppose that webcontainer admin wisely
configures number of threads and jvm heap size. Then you surprisingly blows up
no:of threads that can lead to failures.
and even item 1. is possible there is a chance to saturate web container thread
pool by multiqueries, which will be blocked by "sub-queries". And saturated
thread pool blocks "sub-queries" from progress.
I propose implement this feature at the client side - in SolrJ. It also allows
evenly distribute load on a cluster via
http://wiki.apache.org/solr/LBHttpSolrServer underneath, instead of explode
single node by such multi-query.
> A RequestHandler to run multiple queries in a batch
> ---------------------------------------------------
>
> Key: SOLR-1093
> URL: https://issues.apache.org/jira/browse/SOLR-1093
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Noble Paul
> Assignee: Simon Willnauer
> Fix For: 3.6, 4.0
>
>
> It is a common requirement that a single page requires to fire multiple
> queries .In cases where these queries are independent of each other. If there
> is a handler which can take in multiple queries , run them in paralll and
> send the response as one big chunk it would be useful
> Let us say the handler is MultiRequestHandler
> {code}
> <requestHandler name="/multi" class="solr.MultiRequestHandler"/>
> {code}
> h2.Query Syntax
> The request must specify the no:of queries as count=n
> Each request parameter must be prefixed with a number which denotes the query
> index.optionally ,it may can also specify the handler name.
> example
> {code}
> /multi?count=2&1.handler=/select&1.q=a:b&2.handler=/select&2.q=a:c
> {code}
> default handler can be '/select' so the equivalent can be
> {code}
> /multi?count=2&1.q=a:b&2.q=a:c
> {code}
> h2.The response
> The response will be a List<NamedList> where each NamedList will be a
> response to a query.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
