Thanks Dominique!
So is this parameter generally recommended or not. I wanted to try with a
value of 10s. We are not using it now.
My goal is to prevent a query from running more than 10s on the solr server
and choking it.
What is the general recommendation.
Thanks!
Mark
On Tue, Sep 15, 2020 at
Hi,
1. Yes, your analysis is correct
2. Yes, it can occurs too with very slow query.
Regards
Dominique
Le mar. 15 sept. 2020 à 15:14, Mark Robinson a
écrit :
> Hi,
>
> When in a sample query I used "timeAllowed" as low as 10mS, I got value for
>
> "numFound" as say 2000, but no docs were ret
Hi,
I’m a student working on a personal project that uses SolrJ to search a
database using a solr core that lives on an AWS instance. Currently, I am using
EmbeddedSolrServer() to initialize a Solr core.
CoreContainer.Initializer initializer = new CoreContainer.Initializer();
CoreContainer core
Hi,
When in a sample query I used "timeAllowed" as low as 10mS, I got value for
"numFound" as say 2000, but no docs were returned. But when I increased the
value for timeAllowed to be in seconds, never got this scenario.
I have 2 qns:-
1. Why does numFound have a value like say 2000 or even 6000 b
Hi Solr users community,
We have been doing some performance tests on Solr 5.5.2 and Solr 8.5.2 as
part of an upgrading process, and we have noticed some reduced performance
for certain types of requests, particularly those that requests a large
number of rows, eg. 1. Would anyone have an exp
